Petri

Both, I would say. For users, a cheat sheet; for managers etc. a planning tool. I used to have copies of all "my" users' workspaces, but with tens of them, it was still quite a hunt. So, this "autodocumenting" would be the best solution: "Export Workspace configuration as text" and the result would be a data file like this: workspace_name, item_type, menu_or_palette, position, item

OK. Bugsubmit it is.

I have a viewport, with a custom view, based on Oblique Cavalier 30. When it is rendered, the view changes. Back to wireframe and the view is OK. Tried several rendering modes, same results. EDIT Hidden line is OK. MacOS 10.4, VW 12.5

Yes, but they aren't ideal for locating a particular tool or command. I guess I have to create a useful list myself, like this: Open Rezilla. Open a workspace. Open resource group GSTx. Select all. Say New. Paste. Go back. Open resource group hmnu. Select all. Go to the new resource file. Paste. Export as text. Close both files. Repeat until EOW. Import into FileMaker one at a time. Use replace to add workspace name to all. Repeat until EOSF. Use Find to filter out irrelevant stuff. Sort by workspace & type. Print. Doable, but something of a waste of time. True, but such a beast would help at least trainers, consultants and CAD-managers. Paring down a workspace is a lot easier than adding things to one.

Oh dear... I'm obviously only confusing you! Like this: EDIT The image did not show...

Further investigations show that textures are not exported in VectorScript exports. Well, perhaps I can at least get named texture "prototypes" created, so that only the image import needs to be done manually. Somewhat disappointing.

I'm not talking about plug-ins, but a "normal" item, ie. texture. Why can't NNA document the construct for textures? "A texture is defined by hidden fields which are such-and-such. The values are these-and-these."

Yes, this is of course a problem, as I tried to explain orogonally. Radii cannot be dimensioned simply. One can draw an arc or one can "construct" the arc centre with Edge Snaps (bisector). Both are clumsy and error-prone methods. Therefore it may be more productive to use another approach, ie. dimension what one can (straight sections, if any) and type the radii as text. Radii can be found in the object info, by clicking through vertices. Anyway, contractors do like to know the locations of arc centres for their pegs. If they know the straight section dimensions and arc centres, radii are known, dimensioning them is in fact redundant.

Blink, I was unclear. The "said column" referred to the type column.

OK. Let's see a VectorScript created by Katie.

Hey, Katie! Just ban me, I don't care! Before doing that, please count how many sensible and useful answers I have received from NNA staff lately. Would it be nil or less? Abrasive? Maybe. But you are supposed to be a, what, "Training Program Developer"? Do you have anything to contribute? Can you explain how to create a texture from a data file? What do the Secret NNA Records hold and mean? Can you give ANY answers? Is the berating schoolmistress tone all you can do? EDIT Can you give us anything?

My young friend: I couldn't care less. When kids start to boast about their graduation dates, I lose interest. In your case, even disregarding your arrogant pompousness, you don't seem to know what you are doing. Happy dimensioning.

I'm no authority on VW beyond 9, but... Viewports are just a way of looking at the model. They were introduced in VW 11, I think. Your VW 10 users are able to modify the file (model, data - whatever you call it.) You are then able to open te file with VW 11 or VW 12. With clever use of Workgroup Referencing, your viewports will be intact. You cannot export features to a version that does not support them.

Fine, my young friend! As you seem to be taking your first steps in landscape design (yes, I did the maths), bear in mind that some of us do not do domestic gardens. It's a great start for a young person, though. Obviously the standards in education have dramatically dropped since my Uni years - well, it was another country, too. You don't know trig, do you? Well, whatever: your bucket-and-shovel contractor of the high-end McMansion needs dimensions to the arc centre, to put in a peg for his measurement string. That you can determine without the arc. The radius you may just be able to type. Anyway, choose your dimensioning from this: When you grow up and learn, you may even understand.

I gather that a Hardscape Object becomes a polygon, ie. loses any arcs. Nevertheless, radial dimensioning is not ideal for the site anyway, especially if you do not define the centre of the arc, the location of which is what you should primarily dimension. I have many times redimensioned a project, after discussing with the site personnel about the approach; no big deal, really. The new gadgets (laser devices) also seem to make a difference.

I am about to form an Open VectorScript Alliance. The members would cooperate in reverse-engineering NNA's Hidden Secrets. The Big Fish in our small pond makes it next to impossible for independent developers to work. Undocumented features, strange constructs and the like are the foundation of this monopoly. Did you know that there are "Hidden Records" in files? {Begin Hidden Record Format Entries} NewField('NNAConstant','Family','2',1,0); SetObjectVariableBoolean(GetObject('NNAConstant'),900,FALSE); NewField('NNAConstant','Prototype','3',1,0); SetObjectVariableBoolean(GetObject('NNAConstant'),900,FALSE); NewField('NNAConstant','Version','1',1,0); SetObjectVariableBoolean(GetObject('NNAConstant'),900,FALSE); NewField('NNAMirror','Family','2',1,0); SetObjectVariableBoolean(GetObject('NNAMirror'),900,FALSE); NewField('NNAMirror','Prototype','8',1,0); This is about textures. So far, we can perhaps get this kind of information via exporting a VectorScript, but the Big Brother is watching us and the Firemen are approaching with their flame-throwers. Refer to http://www.opendesign.com/membership/sustain.htm for NNA's stance on similar issues.

They are, aren't they! They are also very poorly documented and many features are a part of the Great Oral Tradition of VectorWorks Elders. Julian Carr (OzCAD) wrote an excellent chapter about worksheets to Janis Kent's VW 8 manual. Now, if we finally would get a two-way connection between worksheet database rows and data records... (I've asked for this only for 10 years and most of the time with the friendly tone NNA considers mandatory for fulfilling wish list items. I've not yet grovelled or licked Texan cowboy boots, though.) EDIT Tone made even friendlier. Now, can we have this feature?

By the way, if anyone wants to be able to save & restore sun positions, I have menu commands for this. You only need to name the sun as "sun" (OI, Data, top field). You say "Save Sun position" and are prompted for a filename (eg. location, month, day, time). Later you say "Restore Sun position" and are prompted to open a file. Send a private message with your email if you want them. They are VERY handy! You can do eg. shadow studies very quickly after saving a few positions. (Donations to Red Cross or similar non-religious charity are encouraged as payment. Every penny helps!)

It would be hugely helpful to have an (editable, ie. text file) list of the commands and tools in each of the supplied workspace. I am continually trying to find commands and tools and there doesn't even seem to be a workspace with "everything". "Auto-documenting" would be a nice feature for the Workspace Editor.

Another vote for this. In European architecture, we even have to consider such oddities as "proportions and symmetry" and they cannot be evaluated & refined in plan views. I'd also definitely want to be able to resize windows and window walls visually, both width and height.

Add a column with the formula "=1", sort by Type, use SUM in the said column. EDIT: To clarify, SUM by Type column!

This has been my conclusion from perusing the texture procedures. I'm not sure which is worse: sit and wait for the next dialog to come or do the whole thing one by one. Maybe I have to forget this - it SHOULD be possible!

Yes, but I'm interested in getting images into VW, ie. creating the textures from an images.

Boy, do I have plenty of questions these days... Is it possible to automate the creation of textures with VS? If I have a bunch (like 3000) colour samples as JPG-files, can they be converted to textures? I could have a text file of the names I want to process. The texture type would be "Image Color".

Yes, having now created 4296 gradients of paint colours in an hour, I know the routine. The gradients actually applied are easy to tabulate eg. for the contractor, but those that exist in the document are not.