dynamic block with user entry

[Anonymous]

I have a basic electric circuit in which I often need to modify its parameters like wire gauge or fuse size. I'd like to do that within a dynamic block by simply typing those values instead of choosing them from a lookup list or using the visibility action. The block can have an initial fixed value the first time it is inserted in the model space and by clicking on it I'll be able to type in the new value. My platform is ACAD 2016 LT on Windows 8.

Your comments / solutions will save me a great deal of time. Thank you very much in advance.

[pendean]

share with everyone your base block (DWG format) and examples of what each variant might look like next to it.

[Anonymous]

SEE BASE BLOCK LINKED.

PLEASE NOTICE THAT THE BLOCK ALREADY HAS A VISIBILITY ACTION. MY REQUEST OF USER INPUT SHALL WORK FOR EACH INSTANCE OF THE VISIBILITY ACTION.

THANK YOU FOR THE PROMPT RETURN

[Imui]

Hi,

Replace text with attributes.

I'we modified your block just in the first visibility state.

[Anonymous]

lmui,

Thank you very much. That was what I was looking for. THe firt visibility state is a particluar case of the subsewquent ones with more than one set of values.

In the case I'd need to enter the same value for all the fuses in the visibility state at the same time what would you suggest?

Thanks again.

[Imui]

Hi,

Try with fields

[john.vellek · Accepted solution]

HI @Anonymous,

Here is a version with all the different visibility states available. You can obviously pre-populate the default values for all of the fuses. Or, as @Imui suggested, they could use Fields that point to a piece of text in the drawing too.

Please hit the Accept as Solution button if my post fully solves your issue or answers your question.

[Emmsleys · Accepted solution]

@Anonymous, 

This process may take some time to set up depending on how many blocks you need to set up but I think in the long run if you have similar projects this could save some time. 

Below is a screencast video of what was done to best capture what I think you want to achieve. 

Attributes were added to your visibility Input groups. Please look to the video below and post back if this answers your question.  

[Imui]

Hi,

This is another way, perhaps this is what you are looking for.

Remember that you need to copy (not insert) the block in order to work

[john.vellek]

Hi aglezb,

I am checking back to see if my post or others helped you with your problem. Please add a post with your results so other Forum users can benefit.

Please hit the Accept as Solution button if a post or posts fully solved your issue or answered your question.

[Anonymous]

Hi John Vellek

I think I need to rephrase what I wanted to do since they way I wrote it definitively misled all the people who promptly had answered to my post. This is what I should have posted instead:

Scenario 1-Not always but more often than not: All the fuses in the diagram will have the same value. What I am pretending to achieve to simplify my work is - for each visibility state - to enter the fuse value just once and this value will be populated to all the fuses in the diagram.

Scenario 2 - very seldom but possible: Not all the fuses will have the same value. - In this case, the replies I have already received are the answer.

So I guess I will have to have two different blocks:

- One block for when fuse values are different: I have this one already. THANK YOU!

- A second block where, with only one input, all the fuse values will be populated. This is the one for which I still need solution.

Note: The letter "A" (form Amperes) will not need to be typed every time so I'll take care of it by leaving it out of the attribute definition.

Thanks again

[Anonymous]

Dear Sara,

I think I need to rephrase what I wanted to do since they way I wrote it definitively misled all the people who had promptly answered to my post. This is what I should have posted instead:

Scenario 1-Not always but more often than not: All the fuses in the diagram will have the same value. What I am pretending to achieve to simplify my work is - for each visibility state - to enter the fuse value just once and this value will be populated to all the fuses in the diagram.

Scenario 2 - very seldom but possible: Not all the fuses will have the same value. - In this case, the replies I have already received are the answer.

So I guess I will have to have two different blocks:

- One block for when fuse values are different: I have this one already. THANK YOU!

- A second block where, with only one input, all the fuse values will be populated. This is the one for which I still need solution.

Note: The letter "A" (form Amperes) will not need to be typed every time so I'll take care of it by leaving it out of the attribute definition.

Thanks again

[Anonymous]

Hi Imui,
Can you show me how to use field in this particular application? I have use them before but for simpler solution like adding the tag name and date-time to a title block.

By the way, I think I need to rephrase what I wanted to do since they way I wrote it definitively misled all the people who had promptly answered to my post. This is what I should have posted instead:
Scenario 1-Not always but more often than not: All the fuses in the diagram will have the same value. What I am pretending to achieve to simplify my work is - for each visibility state - to enter the fuse value just once and this value will be populated to all the fuses in the diagram.
Scenario 2 - very seldom but possible: Not all the fuses will have the same value. - In this case, the replies I have already received are the answer.

So I guess I will have to have two different blocks:
- One block for when fuse values are different: I have this one already. THANK YOU!
- A second block where, with only one input, all the fuse values will be populated. This is the one for which I still need solution.

Note: The letter "A" (form Amperes) will not need to be typed every time so I'll take care of it by leaving it out of the attribute definition.

Thank you again for responding to my post.

[john.vellek]

Hi @Anonymous, You could still do this in one block if that is preferable. You could set up additional visibility states 5 for different values and 5 for same values. You  could use fields in the latter group as described in this thread.

Personally i would leave the A as part of the attribute.When entering the value just don't overwrite the A. That way the text all stays together and has uniform spacing.

[Anonymous]

John,

I agree that both scenarios can be enclosed in the same block. I just have to try i myself to evaluate how complex it would turn, specially if I let someone else in the organization using it.

Now, regarding fields, by using the same field for all the entries in each visibility state then all fuse values will be updated simultaneously? Is this a correct interpretation of how fields would work in this application?

Thanks

[Imui]

Hi,

 i've copied the formula field to each atribute