nam

James, Have you downloaded the 11.5.1 updater?

While double-clicking a script, hold down the "Option" key (Mac) or the "Alt" key (Windows). That will open the script editor window.

Toggle, Check out the Workgroup Referencing feature (under the Organize menu). It does exactly what you are asking. Remember to follow some basic guidelines regarding referencing: 1.) References appear in the target file in a locked state. Don't unlock them and move them as they will move back when updated (they are tied to the origin). 2.) Referenced layers appear in the layer list in italics. Don't draw any new objects on these layers in the target file, as they will be nuked when you update the reference. If you want to draw new objects, do so on non-referenced layer(s). 3.) Moving with the origin in either the source or target file can cause some nasty suprises as well. Try to avoid this. This info is covered in excellent detail in the Learning Series training CDs sold by Nemetschek.

Cross-posted to thread "Embarrasing VW Failures": Ben Supnik? Robin Peel? Sergio? What the heck has this all to do with normal day-to-day use of VectorWorks? As someone who draws for a living, why would you care that multiple exports/imports using VectorScript may cause corruption (see note below)? We have been involved with the design of many buildings ranging from houses to multi-million dollar resorts using VectorWorks (back to the MiniCAD 4 days). Do we see the occasional corrupt file....sure (anyone using the program intensively would say yes). But overall, the application's stability, usability, and file quality is excellent. VectorScript was designed as an easy-to-learn, PASCAL-based scripting language for automating processes in VectorWorks. It has grown to be a robust development platform for both NNA and many third-parties. The "Export VectorScript" function has its uses for scripters, primarily to output a non-binary (i.e. text file) version of the drawing, however I am pretty sure that it was never designed to be used for repeated export/import as you have discussed. Your characterization of VectorWorks as "unstable", "having critical flaws", and that it's "NOT a drawing program but a programming program" just because you are seeing strangeness when attempting things outside the norm is unfair and misleading.

Ben Supnik? Robin Peel? Sergio? What the heck has this all to do with normal day-to-day use of VectorWorks? As someone who draws for a living, why would you care that multiple exports/imports using VectorScript may cause corruption (see note below)? We have been involved with the design of many buildings ranging from houses to multi-million dollar resorts using VectorWorks (back to the MiniCAD 4 days). Do we see the occasional corrupt file....sure (anyone using the program intensively would say yes). But overall, the application's stability, usability, and file quality is excellent. VectorScript was designed as an easy-to-learn, PASCAL-based scripting language for automating processes in VectorWorks. It has grown to be a robust development platform for both NNA and many third-parties. The "Export VectorScript" function has its uses for scripters, primarily to output a non-binary (i.e. text file) version of the drawing, however I am pretty sure that it was never designed to be used for repeated export/import as you have discussed. Your characterization of VectorWorks as "unstable", "having critical flaws", and that it's "NOT a drawing program but a programming program" just because you are seeing strangeness when attempting things outside the norm is unfair and misleading.

Tropics, One of the very best feature of viewports is that they are not obligatory to use. You can carry on with older files and keep your working methodology. As you become more familiar with them, you can migrate towards using viewports (but not necessarily exclusively). Credit to NNA engineers in that they didn't FORCE a workflow change as you suggest. I will say that once understood, viewports are a construct that you will enjoy working with. Secondly, you may want to visit http://www.panzercad.com/. Matt Panzer has designed a utility which converts saved views (or sheets in VW 10 and earlier) into sheet layers and viewports. Hope that helps....

Hong, This is a known bug in 11.5.

The point remains. The 2D Reshape Tool doesn't move parametric objects. That is a shortfall of VW.

You may also want to check the pixel size of the image you are importing. VW will sometimes choke on very large images. If the image is just for tracing, a relatively low DPI setting is fine. If it is intended to print, you can get by with as low as 100dpi if necessary. [ 02-11-2005, 11:58 PM: Message edited by: nam ]