Jump to content
Taproot

Custom Classes - What is your system?

Recommended Posts

My understanding is that 'Site-DTM-Modifier' is not changeable (similar to None and Dimension classes).  It is extremely useful in that placing  3d polygon (and other?) objects into this class turns them into site modifiers.  This is not well documented in the help system

 

https://app-help.vectorworks.net/2021/eng/index.htm#t=VW2021_Guide%2FSiteModel1%2FSite_model_modification_overview.htm

  • Like 1

Share this post


Link to post
On 12/5/2020 at 6:32 AM, Christian Fekete said:

@Taproot do you create a text file and then a .sta file uploaded in VW or is there a prefered process ?

great post, thanks for starting this

 

 

Christian,

 

I'm not sure exactly what you're asking.... as far as creating an office template, we did that in VW directly (no text file). 

Our plan was to use the template as a beta for active projects and weave back in refinements to the master standard.

 

Instead, what we've found is that the "template" is constantly being upgraded with minor tweaks and refinements.  We have a small office, so this is feasible... a larger office would likely not have this level of flexibility.

 

  • Like 2

Share this post


Link to post

I would definitely be interested in a master template CSV file that I could maintain without having to open VW and enter dialogs. I find myself doing some version of that with many things in life (outside of VW). Very quick to edit, and then import. Would kill for that with workspaces too. I just get overwhelmed by all of the tinkering and fiddling with settings buried and scattered all over the place.

 

Edited by Mark Aceto
  • Like 3

Share this post


Link to post

I also like the 9 class limit. Clutter is driving me crazy.

 

Does anyone know if you can have callouts by default to an ANNO class for example? Dimensions do this out of the box, but I really need callouts to do it for simplicity

Share this post


Link to post

For me more classes = more control not clutter. It does require more consideration in how it is set up however. We use hundreds of classes but with a hierarchical setup they collapse down to a list of just 14 lines.

 

To my knowledge you can’t have callouts go straight to a particular class on creation unless that class is the active class.

 

You might be able to create a script using the custom visibility tool that would select the callout tool and place the callout on a particular class. Downside is that after creating a callout it would revert back to your previous tool selection. So to make multiple callouts you would have to select the script multiple times.

  • Like 1

Share this post


Link to post

I will have to look into making a script - pros and con, but it may work for me.

 

The problem I am having with having a lot of classes (for me clutter) is that even with hierarchy I have to wade through especially since VW does not automatically put some objects on a class and I miss selecting the class when creating the item since some and some do not. I am totally with you on the control and flexibility of classes.

Share this post


Link to post
2 hours ago, PLENZEN said:

Does anyone know if you can have callouts by default to an ANNO class

Try using the "Custom Tools/Attributes" command, and check the Tool and Class boxes while the Callout tool and ANNO class are selected.  I believe the downside is that you lose the option of using key commands for the tool, and have to double-click in the script palette to activate.

Share this post


Link to post

Since Custom Tools/Attributes just creates a script, you could relatively easily make a Plug-in Tool from the script and then add that to the workspace and give it a keyboard shortcut. I think you could even remove the original Callout Tool from your workspace and just replace it with your Custom Tool script. But I would recommend keeping the original as a secondary function of the Tool icon.

Share this post


Link to post
1 hour ago, E|FA said:

Try using the "Custom Tools/Attributes"

Yeah this is the one. I mistakenly called it the custom visibility tool in my last post. It produces a basic script. An actual scripter (I.e. not me ) could no doubt produce something more like what you want.

Maybe another workaround option is to make a callout a green symbol set to be assigned to the ANNO class on insertion?

A blue symbol is set to convert to a plugin object or group on insertion rather than stay as a symbol. Might be worth a try.

 

Edit: Yes I just tried this and it does work as a simple workaround. (Should have said a green symbol not a blue symbol tho...)

 

 

Edited by Boh
  • Like 2

Share this post


Link to post

Thanks for all the responses. I'm green to VW but things are starting to all make sense once you ignore the Revit and AutoCad mindset. And VW is very adaptable and allows for a lot of flexibility. Again thanks for the assistance.

  • Like 2

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...