Dimstyle revisited

[Rudy Tovar]

Seems to me that the methods being applied to setting a variable in a dimstyle is either dumb or very backwards.

Based on just minor observation, there still has be an dummy object that consists of all the variables to copy from, or make the dimstyle current and create the overwrite.

Just in general, if only one variable being adjusted being dimscale, then the copyfrom feature would reduce the amount of steps needed to accomplish the same task, or would it even really matter?

Creating one sub-function to create the style and set the variables, the only other thing to do, would be to save the changes being applied to any given dimstyle. So to me it seems that the steps to fasilitate the task wouldn't even matter because of the speed that the sub-function would process it at.

So the only missing setting would be to SAVE the dimstyle with the new settings, once.

(defun make-dim ( name scale etc. /)
;collect-dim-styles
;if-not-NAME-part of collect-PROGN-create-NAME-SET-VARIABLES-SAVE (princ)
)

 

[Rudy Tovar]

I'd like to see your example, but as for not doing it on the fly, it would not work for marketing purposes.

All of my utilities make everything on the fly, this way I reduce having to create a block library and for distribution.

 

[James Buzbee]

Just another way to apply an office standard:

Instead of "making" the dimstyle on the fly, why not create, edit, and save it in a remote drawing and use ObjectDBX to import it when not detected. Thats what I do. If you would like the code let me know.

jb

 

[Rudy Tovar]

Depends on if you're marketing a product.

Remember your product must be global for everyone to use, and must be ready out of the box.

You can't assume that anyone will have a ready template for production. They might just have bare Autocad. So you have to create everything from scratch. As for design center, I don't use it. I custom program everything into my utilities.

 

[James Buzbee]

Hmm. My philosophy is the exact opposite. I would rather have a "Standards" drawing with all styles, layers, etc. in one place for the end user to customize with the local AutoCAD tools they already know how to use. Then utilize ObjectDBX and reactors (or user utilities) to update the active drawing as neccessary.

On the power of ObjectDBX, in the CF NG I'll upload a little utility that I use to import a saved UCS from another drawing. This is something you can't do through the design center. You'll be able to see that with a little tweaking, this utility can be used to import any collections based object.

jb