Rotating dynamic block with fixed attribute orientations

[Anonymous]

I'm struggling with a simple dynamic block.

The block is a simple arrow with 2 attributes.

I gave the block a rotate parameter and rotate action.

This works fine but the whole block with it's attributes rotate.

I would like it when the block can only be rotated to 0, 90, 180, 270 degrees.

The attributes should always be in 0 or 90 degrees orientation.

When the block is rotated in 0 or 180° the attributes should be rotated 0°.

When the block is rotated in 90 or 270° the attributes should be rotated 90°

Anyone know how to do this?

thanks!

[kadmonkee]

attached is a sample

create a block, add Attributes in the properties be sure to leave all attributes unlocked and not annotative

see images

in the block editor provide the parameter Rotate,  then assign the parameter type (increment) see image

provide the action Rotate select only the geometry

the Attributes are free floating and can be manually placed were best suits your needs

[Anonymous]

Thank you kadmonkee for your fast response!

Your example doesn't quite do what I want..

See attatched dynamic block.

I want it that when the block is rotated that the attributes move with the arrow but are rotated so they are always readable (0 or 90° orientation).

[kadmonkee]

i got it.

unfortunately I have not found a way to get that to work the way you want

my example will work with the extra steps of relocating the attributes as needed and will always be readable.

not much help though for the result you want.

[Libbya]

This screencast shows how to do what you desire.  Also, in the same way that you control the attribute rotation angle, you can also move them if desired in order to adjust the offsets.  Probably easier, though, would be to justify the attributes to middle center and place the point/moves there.  Anyway, that should be enough let you tailor it to whatever way you like.

[Anonymous]

Thank you Libbya for the screencast.

You're almost there but it doesn't quite behave like I want it yet.

I adapted the block a little, the problem I have is that when I rotate the block 180° the texts are upside down.

And when I rotate 270° the text isn't readable from the right side.

Is there a way to match the rotation property of the attributes to the lookup table?

It should look something like this:

Attribute rotation       angle1

0                                0

90                              90

0                                180

90                              270

Sorry if I didn't explain it properly.

[hwalker]

Do you mean like the attached?

I took everything off apart from the rotation parameter for the arrow.

I then added a rotation parameter and added both sets of text to it.

I then added a new lookup table. The previous one didn't have the look up arrow.

Check the table for the parameters I used

[Libbya]

---

@Anonymous wrote:

Thank you Libbya for the screencast.

You're almost there but it doesn't quite behave like I want it yet.

I adapted the block a little, the problem I have is that when I rotate the block 180° the texts are upside down.

And when I rotate 270° the text isn't readable from the right side.

Is there a way to match the rotation property of the attributes to the lookup table?

It should look something like this:

Attribute rotation       angle1

0                                0

90                              90

0                                180

90                              270

Sorry if I didn't explain it properly.

---

Ok.  There are a couple things to be aware of.  A double lookup is 'special'.  You have to make the tool and add it to the tool palette in order for the two tables to be linked together.  The tables are linked by having the 'lookup properties' match.  The first table (in this case lookup1) acts as the input to determine the row.  The input property on that table is Angle1.  The second table (lookup2) acts as output and it changes the input properties (Angle2 and Angle3) to the value that is given in the appropriate row.  If you do not have the yellow lghtning bolts, you need to change BACTIONBARMODE to equal 0 in order to see both tables that are linked to the single lookup parameter.

Yes, you can have the individual attribute rotate parameters switch to whatever angle you like at whatever angle or range of angles for the Angle1 parameter.  This screencast starts with your block as you posted it last. 

[Anonymous]

Thank you hwalker for your reply.

This would be my second option.

The texts should be fixed to the arrow.

So the 'position' attribute should always be in front of the arrow.

I'll try your solution too.

[Anonymous]

Thanks again Libbya for your help!

I'll try your solution out today!

[hwalker]

I assume you mean the arrow should always point towards the position attribute.

The problem with that is if you put too much text into the attribute it will spill over onto the arrow.

I shall have a look later on

[Anonymous]

Correct, when the arrow is rotated 180 degrees the alignment of the position attribute should be right.

Same for when you rotate 270 degrees.

For the reference attribute it's aligned left at 180 degrees and at 270 degrees.

[hwalker]

I think I understand what you're trying to do now.

I changed the block. I added a Position and Reference attribute for each of the Cardinal directions. I then added a visibility state for each direction as well.

I changed the visibility states of the attributes so they only show with the correct direction and added the visibility state to the look up table.

See the attached drawing

[Libbya]

Here's another screencast that starts with Hwalker's block.  It allows you to change the attribute values once and have those updated values displayed for each of the directions.  I also added back the rotate grip for governing the change rather than the pulldown menu.  

[Anonymous]

Seems to work perfect 🙂

Is there a way to hide the 'DO NOT EDIT!' attributes in the attribute editor?

Only REF_MASTER and POS_MASTER should be visible in the attribute editor 🙂

Thank you Libbya and hwalker for the help!

[Libbya · Accepted solution]

I do not know of any way to actually hide the "DO NOT EDIT!" attributes.  You can place the 'master' attributes in the block first and they will show up on the top of the list.  In properties you can set them to Preset=Yes and at least they won't show up on block insertion.  Here's one other way to set up the block.  It combines a flip, rotate, and double lookup in order to flip the attributes when in the 180 and 270 degree positions.  Flipping an attribute will flip its justification, but unfortunately each time the attribute value is edited you need to run ATTSYNC on the block to get the attribute position to update properly.  I find that to be more of a pain than the field option, but  you can decide for yourself what block version would work best  for you.

[Emmsleys]

HI @Anonymous, 

Welcome to the Autodesk community! 

There are some great post's in this thread. 

Did any of the posts in the thread help with the issue?

Please use the Accept as Solution for those post’s that helped. It may benefit other users who might have a similar question or issue.

Or post with any new updates if you need continued help on your thread. 

Thanks for your time.         

[Anonymous]

I'm new to dynamic blocks and still trying to figure things out. I used your example to create mine as the actions I wanted were similar. But I am having an issue I can't figure out. Block works fine when I make first rotation to any position. Things go haywire if you rotate block second or third time especially when I make a rotation from 180 to 270. Attributes start to move out and if you continue rotating then the flip parameter doesn't work correctly. Thanks in advance!

[Anonymous]

I was able to get it to work this way. Not sure it is the easiest but it works. I would prefer not to input all coordinates if possible. I am willing to listen to other suggestions. 

[hwalker]

I removed your two lookup tables and added a new single lookup table in which I put the four angles. I also changed the two move parameters to the rotation parameter.

See the attached drawing