Not sure how to add a 2nd visibility parameter, message says
** Visibility parameter already exists in block definition. **
any help appreciated
|
Not sure how to add a 2nd visibility parameter, message says
** Visibility parameter already exists in block definition. **
any help appreciated
Sometimes, i get lost in my own thoughts and need to ask directions to find my way back.
S&D DB Sharing Forum
Can you have all of the visibility states necessary, and a couple of lookups to get just the States you want, from two locations?
Stuck in v2004, can't test it.
Sometimes, i get lost in my own thoughts and need to ask directions to find my way back.
S&D DB Sharing Forum
Thanks everyone for the help/ideas, I will check out lookups (not familiar with them) I am making room tags with room name, like bedroom as vis state then wanted to make floor type like carpet as second vis state below. Not sure if lookups can achieve this since both items are not dependent on the other.
Thanks again,
Sometimes, i get lost in my own thoughts and need to ask directions to find my way back.
S&D DB Sharing Forum
Here is a screen shot pasted in msword of the block to do. You will see I have already made the vis state for the room name. Would like something for the other part of the block so I can insert it, select a room type and select a floor type.
Thanks again
I guess the simple way to accomplish this would be 2 dynamic blocks, which would be fine, just wondered if there way a perfect scenario for the task.
Thanks
You can have multiple vis grips.
ZZ-WeldSymbol.dwg
I've found this, I'm not sure where, but I thought it was from this site.
http://forums.augi.com/showthread.ph...ity-Parameters
Nor have I figured out how it works... and I would welcome any further insight into this.
Last edited by Kernal_CAD_Monkey; 2012-04-20 at 01:54 PM. Reason: found link to original thread
Looks like the work of a user of Andre Lazebny's "Visibility add engine". He poked around in the dynamic block data long enough to figure out how the AutoCAD object model could support more than one visibility parameter (think of them as partial visibility prarameters with their own domain of entities to turn on/off). It is complex, a little buggy, but once you get used to it, you can create great blocks that do complex things and still have a small data footprint. I've been making them for the past six months and they work well.
He created a lisp program that you load when you are in the block editor mode, which adds 12 functions that create/edit the visibility parameters. I had to append his lisp file by creating simple command calls to his functions so that they'd be a lot easier to activate. There isn't robust support for things like undo like there should be, but i can cover a multitude of sins by doing a few steps, use the test block window, rename the block in the test block window, copybase the renamed block to a file I keep my development in, and then I have block in various stages of development if something goes wrong (which occasionally, it does). However, once you've got a block working, the end result is very robust and works well for the end user.
I've been able to do some things with my test block window method that others haven't, like fix a multiple visual DB once I've corrupted it. I can usually get one restored if I try something out of order.
If you would like to know more here are the links:
http://forums.autodesk.com/t5/Dynami...1/td-p/2521041
http://www.private.peterlink.ru/pole...ainypod12e.htm
http://poleshchuk.spb.ru/cad/Downloa...d-eng-v1.5.zip
HTH, Ron.