Dynamic block issue

[Anonymous]

Hi!

Couldn't find a post to answer my question so now I'm posting.

I've been working on a dynamic block. The block consists of about 29~ visibility states all displaying different objects.

In every visibility state I have a rotation action that rotates the object displayed in the visibility state.

The idea is that if I choose one object to rotate the other objects in the other visibility states shouldn't be changed.

I've succeeded in this except from one aspect.

When I rotate an object I want the basepoint (which I'm currently using) to change position according to the rotation, and that is possible when I'm using a Basepoint parameter. But if I switch visibility state after rotating an object the basepoint in the new visibility state will not be in the same location as it was before since the basepoint position has been changed. Is there a way to remove the basepoint grip so I can apply "Move" actions in each visibility state instead?

Too sum it up, i want the basepoint (or move-action) to be different in every visibility state and not affected with what I'm doing in other visibility states.

PS: Since I wont be the only user I don't want a basepoint to be visibility at the sametime as a Move-action is visible since it may lead to problems if mixing them up.

Thanks!

/Adam.K

[pendean]

Dynamic Blocks discussion area:
http://forums.autodesk.com/t5/Dynamic-Blocks/bd-p/154

[Anonymous]

Sorry, was a bit hasty.

Is it possible that any kind moderator could move this thread for me to "dynamic block" discussion area?

[Charles_Shade · Accepted solution]

Only one Basepoint is allowed in the Block at a time. If you apply an Action to the Basepoint in one Vis State it will change in all Vis States.

Point Parameters can be added to DynBlk's without assigned Actions. This is normally used to Cycle thru various Insert points (each Point Paramter acts like a Basepoint).

Remove your Basepopint Parameter from the Rotate Action selection set and it will stay put.

If you want a Move Action to only affect entities in one Vis State you will need 29 Move Actions.

The only way to not have the Basepoint Parameter invisible is to make it invisible in the Vis States you do not want it in.

Please remember to check Solved if your question has been answered

[Anonymous]

---

@Charles_Shade wrote:

Only one Basepoint is allowed in the Block at a time. If you apply an Action to the Basepoint in one Vis State it will change in all Vis States.

Point Parameters can be added to DynBlk's without assigned Actions. This is normally used to Cycle thru various Insert points (each Point Paramter acts like a Basepoint).

Remove your Basepopint Parameter from the Rotate Action selection set and it will stay put.

If you want a Move Action to only affect entities in one Vis State you will need 29 Move Actions.

The only way to not have the Basepoint Parameter invisible is to make it invisible in the Vis States you do not want it in.

Please remember to check Solved if your question has been answered

---

Checked out the tip you gave me about cycling through points. Sounds like a good compromise since it is not possible at the moment to make it as I first thought. Gonna try it out, thank you very much!

/Adam

[Anonymous]

Charles

I'm curious. Just what kind of block are you creating with 29 vis states? Just how long and how much effort is it going to take users to find the correct vis state?

I know as CAD Managers we try to take as much guess work (thinking) away from the users as possible. I'm just wondering if a block with that many options is really useful?

Just my 2 cents

Jim

[Charles_Shade]

Don't know. The OP seems to have this need.

[Anonymous]

In this specific block I do, if you wanna know more specific each vis-state is a different symbol that is used on our drawings to mark a component/alarm sensor.

Thanks!

/Adam

[Anonymous]

As I tried to suggest in another post, that many Vis States per block will probably result in serious lag if you have lots of them in one drawing. As another user pointed out, that's a lot of choices for any user to have to sift through after inserting your block. You may want to see if you can cut it down to 6 to 8 blocks with only 4 to 6 vis states each. For example, more than one of these Vis States may be more popular than the rest, which would suggest more than one block. Your symbols might have groups that use a circle, while other groups use a rectangle, and still others use a diamond or something else.

You stated in your other post that you are fairly new at AutoCAD. You'll find that after all your hard work, it will become a nagging problem to insert a block at the initial state, only to have to consult a long list to change it to something else -- it's time consuming. Other posters will also tell you this, and it's because at one time or another we have all jumped in with both feet only to find we created a monster lol...

(Joy and pain -- sing it with me now -- sunshine and rain...)

[Anonymous]

Molman is right. After working in CAD for over 20 years, you learn a few things.

Anything over five clicks is going to cause whining and crying.

Users are dumb and lazy.

And KISS is king.

The more choices and the more thinking users have to do, the more errors creep into a drawing. The primary job of a CAD Manager/Guru is to let users get on with the job of designing and keep the CAD side as simple and fast as possible.

[Anonymous]

---

@Anonymous wrote:

As I tried to suggest in another post, that many Vis States per block will probably result in serious lag if you have lots of them in one drawing. As another user pointed out, that's a lot of choices for any user to have to sift through after inserting your block. You may want to see if you can cut it down to 6 to 8 blocks with only 4 to 6 vis states each. For example, more than one of these Vis States may be more popular than the rest, which would suggest more than one block. Your symbols might have groups that use a circle, while other groups use a rectangle, and still others use a diamond or something else.

You stated in your other post that you are fairly new at AutoCAD. You'll find that after all your hard work, it will become a nagging problem to insert a block at the initial state, only to have to consult a long list to change it to something else -- it's time consuming. Other posters will also tell you this, and it's because at one time or another we have all jumped in with both feet only to find we created a monster lol...

(Joy and pain -- sing it with me now -- sunshine and rain...)

---

I've actually been thinking about this before I made the block aswell. I've speculated and I've tried every possible thing and idea that I've had. Can't think of a simpler way to do it.

And due to my own experience and what I've understood of my colleagues oppinions this is easier to work with then before.

Maybe it can be done better but right now it works.

Also I'am making this block for my own benefit when working, I'am the user in this case.

Maybe in the future I'll make them blocks that has it all, but for now I'm satisfied

Thanks!

/Adam