RickR

You might check your workflow. Can you describe your steps exactly? I can't think of anything reason or method for a Polygon to turn into a Rectangle. I do the reverse frequently.

I'd love to see some nodes for selecting and manipulating objects. The existing tools could use some flexibility. I recently imported a PDF and wanted to select thousands of very small lines from an exploded hatch. I thought a little network might do the trick. Nope! (I eventually found an old Pat Stanford script - thank you!) Then I wanted to select some objects based on their coordinates. So I went to Pat's relatively script to see if I could tweak it. Well, I'm sure he can. I really don't want to learn VectorScript and Python AND Marionette.

As pointed out by zoomer and others, there are issues with the ease of wires snapping to nodes as well as issues with the debug tool not picking up wires. I've decided an large amount of the problems are related to object snapping. Nodes have outlines, text and circles in addition to their actual snapping points. It's far too easy to snap to something else! Perhaps the Node tool could disable several snapping modes, and/or nodes could be made simpler. I'd hate to see them all be raster graphics, but is would minimize the issues greatly. I've also notice it's easier to work with a node if it's been brought to the top of stacking. It's become a habit to ctrl-F to change a node. I've also started disabling several snapping options, object snapping has to be on, but none of the others help.

+1 Why should any palette not be dock-able??

+2 There are several dialogs where you have to click one thing in order to click on something else. I call that poor UI design!

This has been wish listed previously, and probably repeatedly! I vaguely recall something about it in JimW's discussion of 2017 improvements.

One for the wish list!

+1 Expand the descriptions too. Many are written in 'coder' speak rather than plain language. Include formats and limits of inputs and outputs.

I vote for the whole OIP to be updated. -collapsible sections or more tabs -uniformity across objects of both data available and of organization -visual render settings (too many drop-downs) -data tab, all above, requires way too many clicks, how about in place editing? -include pen/fill attributes! (with a 'revert to class type' button) and that's only a few minutes of thought!

There is a concept in User Interface design generally called 'consistency'

Only works when wrapped in an Object. I forgot "only". Thanks Alan! You do quite well at video tutorials! I'm sure they will help many others as well.

2 quick questions 1. How do you define something as Control Geometry? I think I've missed something basic. I have used named objects to link to, but CG seems to work differently. 2. What is the difference?

Several comments here imply Unified View is an issue and should always be On or Off. I use Saved Views to help manage UV and Design Layers. Some views have multiple DLs in 3D (at the same scale) and some views are of other DLs at other scales with UV off. Jumping back and forth isn't a problem.

DL scale affects page scaled elements: - Text size - Line weight - Symbols with "page scale" set also DL page size (Some only print from DL.) Something like DL scale is required, unless you never use any of these elements.

Your assurances about breaking old files is fine, but worries me quite a bit. My work and I suspect most other users is 'project based' meaning most files are inherently time limited. Granted some projects are multi-year, even in my little corner. Keeping a broken tool in case I have to review an old project is a poor trade off. Updating minor parts to adapt to new features is a small price to pay for getting rid of old issues. "We've always done it that way" is a weak argument but a strong blockade. If something looks funny on import (warnings?) then it would be much simpler to have old versions available. Other software I use does this, and it's not such a big deal, except for licensing issues. And I'm sure there are other solutions. On other subjects - I too support your efforts Jim, in getting the rest of the company to see things from our point of view. This has been quite an interesting thread!!

Your basic method works fine just as you described. I did a quicky test. Modify the worksheet criteria to make sure you only have the polygons you want. In this one I set "Name" is not blank.

I've not seen it, but haven't done much detailed export in 2016. Check into whether you are exporting from Design or Sheet layers, and whether you are exporting into paper space or model space. That confusion got me several times!

I suggest you try to make that a Tile, rather than a Hatch. Best to review the help on Tiles before jumping.

As part of this it probably makes sense to decouple the 2D plan fill setting from the 3D fill. (other than textures)

Maybe, I suspect a Python/Script command is stuck rather than the whole program. It seems to lock up in some editing mode. Maybe group or roof, but the return button has no text. Most menu commands can still function and I can get out of whatever mode it is in, but something is still off.

There are many answers to this, and I use several. None of them are quite like what a Spotlight instrument can do, so much depends on your real goal. 1. Make worksheets that list the trusses rather than tagging them all. You can list any of the truss OIP record fields as well as general things like X, Y, Z coordinates. See https://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=211698#Post211698 2. Make truss symbols. See a very similar discussion: https://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Main=44347&Number=222982#Post222982 I haven't tried it but I suppose you could make them all Lighting Positions and get a lot of tagging functions. They have to be symbols first. 3. Make trusses fixtures (again make symbols first then convert to fixture, accessory type is best) Similar to the above but now you have all the Label Legend tools. The drawback is that you really can't get to the truss specific data (length, box, cord) but you can put in whatever you like, especially the user fields. 4. Use a Tag symbol. See where someone wanted to tag walls: https://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Main=45231&Number=228162#Post228162 They wouldn't be directly connected to the truss but tag symbols would give you the most graphic flexibility. 5. Make a wish list item and wait. I would love to see Label Legends for lots of other things. Truss, decking, speakers, curtains, tables/chairs, etc. 6. Make a Marionette object that does what you want all in one step. Probably not a practical answer but it has a lot of possibilities. I just made a tool for Traveler curtains that shows stacking space calculated from the specific track dimensions. What looks good to you?

Teal is a 'hot' color the last few years. I'd say the graphic designers are just following the popularity trends.

Not to rain on the parade of ideas but I see doing this now with sub-classes; "Box", "Box-lid open", "Box-lid closed" A built in tool should be vastly more powerful. And I don't want to rebuild every door & window & cabinet &&&&

I use layers and classes for multiple levels all the time. I believe this is how VW is designed to run.(and most other CADD) In a viewport it's pretty simple to flag a class as being dashed rather than it's normal look. I also put odd levels like balconies in their own classes, but using their own layers is pretty simple too. As for organization there are 2 things that make it simple. 1. Label stuff with meaningful names; "ground plan" is too vague, try "stage level set plan" "house mezzanine floor" "light onstage electrics plot" and call viewports "viewports", saved views "views" it saves having duplicate names with sheets and layers. 2. Make many saved views. By automating the on/off settings all the layers and classes start to make sense and you save time. Here is a related tip: make a saved view for every planned viewport.

You are seeing errors that don't show on my system at all. Is this because you don't have Spotlight? Do you get SoftGoods objects in Architect? FYI: I don't think there is value in getting this to convert to an object. Without complete control of the curtain objects I will still need to to get to them individually. Others may like the simple utility of showing the stacking space, but I need to go deeper. (worksheets and renderings) I appreciate the help in debugging!!