In the Dynamic Interface

Lookup Range Function

As many can see the Lookup tables is one parameter that has many functions. The one function I use a lot for my dynamic blocks is the Range function inside the lookup table. The block attached has a simple example where users can hookup a block place holder field inside an attribute to a linear parameter. As you stretch the block out, then regen, you will notice the field will update and tell you where you are. The syntax for creating these range functions is pretty simple.

[10'-0",11'-11"] This simple format allows you to specify a minimum on the left and a maximum on the right. Then once your parameter falls between these numbers your block place holder field will update per the lookup properties.

The AutoCAD 2006 help has some good information regarding these range Functions.

Click here to Download a sample drawing:Download range.dwg

How do I keep my BASE POINT centered?

I received this question via MSN Messenger from a fellow BLOGer and thought I should post this for others also. If you have a dynamic block where you want your Base Point to ALWAYS be centered with your block, take a look at the attached block.

Example: Say you have a table and you have a stretch parameter on one side of your table. You stretch the block to increase the length of the table. And now you cant get the Base Point to stay centered. Well if you insert a BASE POINT parameter in the MIDPOINT of the table. Then associate a Stretch or Move action with the .50 distance multiplier set. Your BASE POINT will stay centered in your block. Its a nice little way to manage your BASE POINTS for Dynamic blocks.

Check out this block attached to see an example:Download BasePointMid.dwg

Dynamic Block Tooltips

As I've said before in previous posts, AutoCAD 2006's Dynamic blocks are great!! But sometimes you hit that point where too many Dynamic block properties start to confuse users. Once they use the block for a while they get comfortable with what each grip does. But even though the grips have different looks to them, you know what they do in general. But you don't know what they actually do to the block. So one idea I came up with is to use the DONUT command and create little DONUTS at each of your Dynamic block grips on the DEFPOINTS layer. Then issue the HYPERLINK command and in the "Text to display" type in the explanation of what this Dynamic block grip does. Then close the block editor and hoover over your Dynamic block grip. You should see a little Hyperlink Tool Tip telling you what that Dynamic block grip does.

Note: Many will probably try to add a hyperlink to the Dynamic block grip. Unfortunately this wont work. This would of been a really easy way to get tool tips. But we work with what we can get. Hopefully in the future we'll get some help strings. But for now this should help a little bit. Make sure if you include this little trick in your blocks to RE-Specify your selection sets for actions so the DONUTS will move with your block. The FLIP parameter I've noticed works great for tool tips!! The linear grips you need to hoover around a bit to get the tool tip, but still works.

Here is the location to type in Dynamic Block Grip descriptions. Make sure to provide some character in the "Type the File or Web page name" area. Or you wont get the OK box.

Here is the Tool Tip that appears when you go to grip select a Dynamic Block Grip. Unfortunately the CTRl + CLICK to follow link is always displayed.

Here is the DWG to look at. Download Tooltips.dwg

Publish Block Data to DWF

With the great new addition of Dynamic Blocks in 2006, we also got a nice new tool that allows you to Publish Block data. This block data can include Dynamic Block data or simply just block and attribute information. To set up your DWG for block data publishing issue the Publish command. Then hit your publish options on the left. Now you'll enter the publish options where you see at the bottom Block Information and Block Template File. Next select the Block Template File pull down and select create. This will bring you into the Publish Block Data manager. If the drawing your working in has some Dynamic blocks or attributes, you can hit the Scan for Blocks button. This will populate the 2 columns below. In the bottom left column you'll see "Check Blocks to Publish". The blocks that are checked will be published to the DWF and now prompt you in the bottom right column to "Check Properties to Publish". This option will publish Dynamic block properties such as Linear, Visibility, XY, Lookup and more. If there are more blocks you'd like to add to your Block template file you can hit the Add button and add more drawings. Once you get all the blocks checked you want, simply hit the save button and save the Block template file (.BLK) to a location where you can access it when publishing DWF's. Once you save the template file just make sure your Publish options for Block Information is set to Include. Make sure your pagesetup is correct and hit the Publish button.

Parameter & Action Text Size

Have you run into a problem where your Parameter & Action text is HUGE when you enter the Block editor? The Parameter and Action text works off the Zoom scale your at. So if enter the block editor and you're really far out from you objects you probably will have a bunch of overlapping parameters & action text. And if you issue a Regen at the far zoomed scale you will see no difference. But, if you zoom closer to your objects and issue Regen again you will see the text start scaling down. Making it easier to read the text. There also is a button on the Bedit Toolbar that will do a Parameter and Action text regen. Either method works. Now when you have a really complicated block with a lot of parameters my method is zoom really really close, issue a regen then work with your block.

Another system variable is BPARAMETERSIZE. This adjusts the scale factor for the regens. It's currently defaulted at 12. So it you find it too small try bumping up this value to somewhere around 20. There also is a system variable called BGRIPOBJSIZE that controls the grip size in the block editor.

Lookup Tables not Working part 2

Well after doing some research on user problems for the last month I've noticed many have been running into problems with getting the Reverse Lookup option. In order to get the Reverse Lookup option enabled you need to match values in your Lookup Properties and your Input Properties. The image below values DO NOT match. You can see there is a Input value for 1" and a lookup properties for 1 Inch. Then you notice there is a Input Property of 2" but no matching 2 inch lookup properties.

Now if you add a properties to the lookup properties as 2 Inch. Then select the Read Only button you will now get the Allow reverse Lookup enabled. This option will allow the Lookup tables grip to be active in your drawings.

"Move Up" option in Visibility State Manager TIP!

The "MOVE UP" option in the Visibility state manager is a very quick way to add multiple Dynamic block references of a visibility state. I think on major thing 2006 is missing is the ability to change visibility states at insert. So, I decided to make a Dynamic block of each visibility state in each of my blocks. This allows our users to insert a block and not have to manually change visibility states after insertion. But still allows them to change visibility states if necessary once the block is already placed in the drawing.

So how to use the move up option. Say you have a Dynamic block screw that is 2" long. Then you make a visibility state for a 3" 4" and 5" screw. The dynamic blocks name is "SCREW2inch". Then in the block editor you use the "SAVEAS" button and name the block as "SCREW3inch". Then open the visibility state manager and select the 3inch screw visibility state and use the "MOVE UP" button to place it at the top of the list. Then use the "SAVEAS" button and repeat for each screw size. Now when you insert the block called "SCREW3inch" you will get the correct size at insert and still have a Dynamic block with all screw sizes. Does this save you a TON of time, probably not. But when you have screws that are 2" 3" and 4" long, I've seen that users sometimes just forget to change the visibility state of a screw from 2" to 3". Since they are so similar in size.

"BLOCK HEAD" Dynamic Block Contest

Well Shaan Hurley posted this on his BLOG. "Undisputed KING of Dynamic Blocks". Pretty funny. http://autodesk.blogs.com/between_the_lines/2005/04/betablocker_win.html

I just found out the Dynamic blocks I made for 2006 won 1st place in 2 out of the 3 categories hosted by the Autodesk beta team. I've gotten a ton of e-mails lately asking to post the blocks I created. And thought why not post them for others to check out. So hope everyone likes them. The SW block was by far the hardest to create and the Post-Tension block is the best block we have.

Post Tension Dynamic Block.

This Dynamic Block is a Structural Post Tension Tendon Dynamic Block. A post tension tendon is a steel cable that is embedded in the middle of concrete slabs. When AutoCAD 2006 was released most users went straight to their old legacy block libraries and started converting their 2000 old legacy blocks into 1 Dynamic block. I think it is great. But what happens once you convert those 2000 blocks and are left at a point where you have nothing else to convert to dynamic blocks? This is the time to start digging into your company LISP code. Yes, who thought Dynamic blocks would start cutting away on a companies LISP code. This one block alone has cut about 5 or 6 of the longest and error prone LISP code we have. When using LISP code its great for the initial instance of the block but once something changes the user has to manually re-run the LISP code again to generate all the correct information. This block uses NO LISP code and is totally user friendly. With this new dynamic block we’ve cut our time creating our foundation plans by more than 75% leaving us extra time to focus on other aspects of the project. This block also has a huge lookup table that has all our length conversions using the range function in the lookup tables.

Download posttension_dynamic_block_standard.zip

SW Dynamic Block.

"This Dynamic block is a Structural Shear Wall Dynamic Block that has had many revisions due to the growing power of Dynamic Blocks. The Dynamic Block uses a combination of Visibility, Point, Lookup, and Linear parameters. There is a Total of 16 Parameters and 19 Actions. The block may look very intimidating at first but each parameter and action set is utilized to its fullest to perform to a users needs. When opening the Dynamic block in the Block editor it immediately shows that Dynamic blocks take time to learn and perfect. This block explains it all, the Dynamic blocks are almost too powerful at times but with many revisions it has been the most powerful one we have in our Dynamic Block library. There also is a Linear parameter in the Block Editor called S.W. Symbol Length that is stretched way down in the editor. This is designed this way so we don't have to use a Flip parameter. Since the Flip parameter re-justifies attributes when flipped we don't have to worry about modifying a block when the attributes are moved. This allows a user to stretch the block to the other side of the wall with ease.

Download 033105shearwall_dynamic_block_standard.zip

I've also been asked from readers of this site, to create a page where users can post their blocks for others to see. If anyone has some intel on how to accomplish this, just send me a e-mail. Hopefully soon Autodesk will have a gallery for users to post blocks. This is how I learned the Authoring process of Dynamic Blocks.

Chaining Actions

Out of ALL the dynamic blocks I've made, and all the different properties I've used, by far the most complicated ones deal with Chaining. I really hope sometime here soon we'll get some good examples on how to use the Chaining feature. Because I for one struggle each and every time I need to use it. I pretty much just try to stay away. The most complicated part I find is trying to decipher which parameters should be set to allow chaining "YES" and which ones should remain set to "NO".

When the Chain actions property of a parameter is set to Yes, the actions associated with that parameter are activated when that parameter is changed by another action.

Make sure to be careful not to inadvertently select the geometry which the chained parameter affects when adding a chained parameter to the selection set of an action. Otherwise some actions may be performed twice on the same geometry. This will cause geometry to move really quickly and mess with your block.

Attached is 2 examples I have using the Chaining option. I've made a good of blocks and these are the only 2 blocks I have that use this option. So, if your blocks don't have any chaining options don't worry about it. If they need them good luck!! Feel free to e-mail your block when working with Chaining and I'll attempt to help. Download chaining_example_1.dwg

Lookup tables not working?

I received this question via e-mail and wanted to answer it here for others to see also. One reason why a lookup table wont work is your lookup table status. Once you populate your lookup tables there is a option down on the bottom called "read only". In order to see the lookup table grip once you close the block editor this read only option needs to be set to "Allow reverse Lookup". When ever you add a lookup row or sometimes modify some values it might pop back as read only. So, make sure to glance down when your done editing your lookup table to make sure the allow reverse lookup is checked.