Petri

Considering that in many cases practically all VW objects have a fill and that one usually only wants to send the "hard data", my feeling - and experience - is that "No fills" is what one normally wants. "Invisible classes not exported" is a good way of controlling what one sends - again, one does not normally want to send everything. But these are matters of taste, workflow, QA procedures etc. Unfortunately it seems one can't even script the settings: the Application Preference Selectors (poorly documented in the Additional Resources of VectorScript Help) do not seem to include these choices.

Tsk tsk. Are you allowed to claim ? here? I'm not. But a nice script anyway! Why do you exclude dimensions?

OK, I tried, but to no avail.

Zip it before emailing. DWGs usually compress very well. There is something strange in VW's DWG-files: they can be several times bigger than same data saved in AutoCAD.

Possible, but of course it'd be easiest to substitute all with one font. (Typeface, to be exact.)

Another useless PIO... This is because NNA believes that users cannot type the number of chairs they want, so a pop-up list is used and this interface device only does text. Changing the field type to number does not help as the script of the PIO expects text. (Tested already years ago.) Well, one can always export data to Excel or Numbers.

The DWG-export settings are not saved across sessions.

Could be scripted fairly easily. (Not a bad idea at all. Pity I'm not allowed to publish scripts here.)

Does it? Where? (I can't wait to see a user to flip the grand piano so that it fits the layout...)

Really? Using that, if I'm working on a house, I always get the Schr?der-Schr?der House; if an apartment block, the Aalto Hansaviertel building; if a public building, Mies's Barcelona Pavilion and so on. Nothing random there.

Why do users need to uncheck things like - Export 2D Fills - Export Images and Image Files and choose - Invisible Classes are: Not exported? In the real world, few users wish to have these as NNA has defined The Correct Procedure and many users' exports fail because of these settings, causing confusion, frustration and anger, not to mention endless calls to tech support. At least I don't suggest exporting "drawings" but "data". Why can't these be a part of VW Settings?

UseClairvoyance(PageLocation, x1, y1, x2, y2)?

I'm sure you have a reason for this, but I'd be curious to know what it is. "Us programmers" (yeah, right!) avoid changing the user's clipboard like a plague.

No, I don't. They are completely useless in Finland. EDIT Further clarification: we do use the Stair tool the way Christiaan describes (2D only) - but I am thinking of reviving my own one so that we would not have to convert the unacceptable graphical representation on the NNA stair to lines that we then edit. In my role as a VW consultant, I can hardly justify VW Architect to prospective users. Wall styles are pretty much the only useful feature and even that does not have all the necessary features.

Have you tried setting a "junk" value first, before reading user input? I have a vague recollection of getting something remotely similar fixed this way.

So far, so good, but I haven't tried too many yet. Reading the list of obsolete functions is a frightening experience, though. No new ones this time, but I have tens of scripts with functions marked obsolete several versions ago and one day the axe will fall.

A generic DTM data generation script - as the one mentioned above - may also fail if the programmer has not anticipated the notation used. Surveyors are a suprisingly imaginative group of people! A particularly nasty and practically impossible notation is one where there is a cross and two separate text items, like full metres on the left, decimal part on the right.

Does it? I can get it to use just a displacement vector, not to follow a path.

I can't think of a single NNA object that would be usable in our architectural & landscape design practice or in the practices I deal with as a VW consultant.

Does that do the trick? Never realised...

I think this is intentional & by necessity. This is the result from the New Rotateable Rectangle, which stays a rectangle regardless of its angle. Just get used to it - by and large, the Brave New World is better than VW 12 in this respect.

If you can't find freeware, ask your distributor to ask Ultirender. There is such a script in the Finnish localisation.

Charles, Are you using RealDialog & Numeric field type?

Pete, There is of course a hidden agenda here: I'd like to be able to connect to external databases and having "internal" SQL would be one step to that direction. (Whoops, it's no longer hidden!) Why? Well, take the new Plant Database. As I've reported, the Plant tool does not use the database but text files generated by the database. If the database is updated, one has to also remember to regenerate the text files - which can only be done from VW & the Plant tool. Not going to happen in real world. Otherwise I don't care what syntax is used as long as can be used & works - and is a bit "hidden" from Joe. The current syntax is, I think, even more cryptic than SQL.

To Joe Average, such a pulldown list would read WHAT. That's why I suggested the advanced mode, e.g. SQL.