I’m revisiting a topic from a while back. I’ve only had time to post it now. The issue is with text scaling.
Things tend to get out of sync. The first picture compares basic Rhino text to VARQ’s section text:
Basically, what is happening is that when the “model space scale” changes the text in (most) VARQ follows along. This is mostly an unwanted feature because objects (such as the section mark symbols) DON’T scale. The objects and the text are out of sync.
Creating a VARQ style requires you to basically create your own text style for each and every style of each and every object:
And worse yet, things can easily get out of sync. When you update a vaPlanView you don’t necessarily want the text to change. And any Rhino text won’t scale. This makes things incredibly hard to manage.
I previous suggestion was to simply not use the “Model Space Scale” feature:
This doesn’t fix all the issues mentioned above and creates a new issue: We’ve now quadrupled the time it takes to create just a basic template (without yet even considering VARQ Objects).
The bigger issue arises when one realizes that they need to now create every type of VARQ object for every possible scale they might use. If something changes you have to go and change every single object; every single attribute one-by-one. It’s impossible. Using the stairs as an example: If you want the riser text to be correct you have to create a different stair style for each scale… for each style of stairs… There’s no point in having the user specify the text when the program just changes the text height on the user (which is not in line with the host program’s behavior).
One more thing I’ll tack on is the outlined objects appearing on vaPlanViews:
The only way to deal with this is to place your sections on a “no plot” layer and place “dummy” objects over top of them. This is actually manageable but just one more thing…
CAD standards from way (way) back in the day would require a different “style” of each object for each individual scale. Rhino makes this easier by allowing the user to simply adjust the “model space scale” and not have to edit each individual option one-by-one. This works just fine in my opinion: Slightly more work than ACAD’s annotative objects but less variables to have to worry about. 20+ years ago, drafting was much simpler, so the tedious task of creating styles for your text, dimensions, leaders, etc… was horrible but achievable. Asking users to take a step back… 30 years… there has to be a better way.