Owen Walz

++++1 Unfortunately class settings won't reproduce a view. Sounds like Vectorworks needs a solution for this. Ideally this would be to leave the camera instance in place, and allow it to control multiple viewports (i.e. multiple views can be updated in one shot if the camera is moved / adjusted).

I'm wondering if there's a way to reference one camera with multiple viewports. IE I'd like to be able to update the perspective of multiple viewports (with various class settings) at once. This is typically an option in 3D rendering software, but I haven't found a method in Vectorworks yet. Correct me if I'm wrong but once a rendtrworks camera is linked to a viewport it cannot be linked to another viewport.

+1 Great thoughts all. Love having full screen on the mac now. Can't wait for some docking options.

I'm wondering if there's any way to emulate the kind of palette toggling seen in products like Creative Suite. I find working with VW on a laptop pretty frustrating given how limited the screen real estate is, and how cumbersome it is to position, close and restore palettes. Is there a script for this? Is this a feature in the works?

I have a project that involves flattening some section viewports for a colleague who can't deal with 3D. I did this with one, and it worked beautifully. Section hatches, most polygons and fills and all came through okay. I did it to another with the a viewport with the same settings, and the sectioned solids lose their fill. And they're reduced to lines instead of polygons. Any ideas?

Or on that note, a way to map the constrain to working plan snap? Seems to be missing from the keys section in the workspace editor.

Thanks guys. I'll take another look at these options (screen plane, constraints). I hear you Jim. Shift does seem to lock to an axis, but doesn't always prevent snapping to / movement along the unseen axis. Any chance there's a way to map a keyboard shortcut to switching to / from screen plane, in case that's the best solution? Haven't found one yet. Maybe that's an advantage to working planes.

I'm wondering how to ensure that I'm only moving an object along the axis that I can see with a given view. IE, if I'm moving an object in 3D from a side view with no perspective, movement is limited to Y and Z axis, or if viewing from the top, Z movement cannot occur from snapping. This seems to happen on its own some of the time, and other times I move something only to find out it's slipped into another location in the unseen dimension. I've tried holding shift, and this doesn't seem to solve the issue. Any particular sort of workflow or plane setting that would help with this? Thanks, O

Thanks guys. I hadn't considered the layered viewport option, and resorted occasionally to the annotation solution Michael mentioned (and always worried I would forget about updating it when I change geometry). Sounds like a feature request maybe? I imagine this being added as an attribute to classes, i.e. a 'section style' in addition to the standard line and fill options. That would be pretty great. If the roadmap is moving towards 3D and generated sections, this kind of granularity would be necessary.

Thanks Jim. This would be super helpful for entertainment designers.

I'm wondering if there's anyway to have section viewports generate a few different styles for the sectioned objects (i.e. denser hatches for certain objects, lighter line weights for more detailed pieces). I see there's an option for different classes for 'structural' objects, but I don't see anyway to specify what objects are 'structural.' Ideas? Thanks.

+1 Oh man this would be amazing.

Thanks! That works. Would still love to know if there's a list of these codes somewhere.

+1 Seems oddly missing considering all the other issue management tools.

I seem to remember that there is a way to create a record field / linked text that updates to the current date, or publish date. Is this some kind of short code, suffix or prefix? Is there a list of all these codes somewhere?