maarten.

It works fine here...

Gerrit , is there a reason why you unlock that Guide? I thought that the purpose of a Guide was that you couldn't move it accidentially?

When you change those parameters, the classes will change from "none" to the ones you fill in (not sure about all though, only have tried one)... BUT it will not be visible in the dialog, there it will still say "none" cause it's not programmed that way (i tried it out (i don't use that pio anyway, so it wouldn't matter if it wouldn't work anymore)). On a side note: I personally wouldn't start messing around and changing other one's pio's, especially not when they are locked and when you have to use them on a daily base. If NNA don't want you to change it, they probable have a reason for that.

Agree! I understand why NNA did this, to have some kind of logic in it, but believe me, this logic really isn't an advantage. So i agree with you! But i would even go further than this, i posted it on the Ducth forum ones (without much "hoera for that" though ): The possibility to use normal keys as modifier. For example, i would like to give all my Architectural tools a shortkey like this: A+W for window A+D for door ... The possibility to use double keystrokes as a shortkey: one time "&" is text two times "&" is rotated text ... Double right mouse click: OK the dialog Double scroll weel click: move page (for example of course) And shortcuts to the pallets would be useful too! For example, when you select a pio and you want to change a parameter, you now need to use your mouse to go to there... I would like to have a shortkey to go to there (for example alt+tab). That's much faster then using the mouse (especially when you have a big screen (and i guess most users have that nowadays)). And last, but not least: expand the pio's with intelligent keys (ctrl(command), shift, alt) when using the tool. For example: when you draw a line and hold down shift, you'll draw a line under a curtain angle, when you make selection crossing over some objects while holding down alt, you'll select all the objects that "though" that crossing,... So, let's expand that use, it's very useful! For example: the rectangle tool: while drawing, you can hold down ctrl to switch mode (rotated - straight rectangle). Just like the eyedropper tool has, it's very useful! When a symbol or pio is in a wall, it would be usefull to "lock" them in the wall so they wouldn't flip out of the wall while moving them to an other place. For example: select the pio and hold down the mouse button, press tab and fill in a value, hold down alt and loose the mousebutton => the pio moved and is still in the wall. I know, you can change that one mode in the mode bar... You can even link shortkeys to those modes (very handy btw), but i would like more ways of doing such things. And skip the rotation part while placing pio's by point. Now, when you're placing a pio by point in your drawing, you have to click two times: ones to give it it's location, and a second time to give it it's rotation. I would like to be able to skip that rotation part by holding down the alt key while placing that pio (so that you only have to click one time) IMO, the mouse should only be used to draw, not to click on icons, go to menu's or go to pallets... And it's to bad that VW is mostly programmed that way that the only possibility is to use your mouse to go to those places... I really hope that NNA will take an other look at their shortkey-system and make it easier for the user to adjust and expand... I ran out of logic shortkeys years ago... I have to let go shortkeys for other ones quite often because there are non available anymore (well, no logic ones that is)

I think it's this one: DoMenuTextByName('Guides',1);

You can copy the setting files (application support/VW/2008/settings) from your computer and paste those on the new computer... That would save you some time allready, but there are only a few settings in those files, so i agree, it would be cool if VW would remember all the settings. So instead of only save the layout and modes in an extern file, VW could also save all the pio preferences in an extern file aswell.

when you ungroup that door, you'll see that the poly that will cover the "ground" is in the class "Door-Main". So normally when you'll give that class a fill, everything would be OK. But as you'll notice, that poly doesn't use the class attribute as filling. It's hard coded to use no filling... Don't know if it was meant to be this way, or that it is a bug?

sorry, i thought you were talking about a selfmade plug-in object. But i see now in your screenshot that you're using a spotlight plug-in, so nevermind my post.

It has been requested here. I really hope that this will be a part of VW soon. With the big screens of today, tabs aren't nesesary anymore, and will only cost more time to navigate IMO.

It has been requested here, so hopefully it will be a part of VW someday...

You can also get this error when the parameter 'LineLength' is NIL (i had it ones, but i can't seem to reproduce the error) or when there's no standard value filled in for the PIO's parameters.

I had this in my previous post, but for some reason it wouldn't show, so I cutted it out. But i uncluded an example, and it had some strange characters, so I'll try again, this time without example: If you find a not-encrypted plug in, change it's class, and then open that plugin-file (the .vso file) with texteditor, you'll see the name of the class right after the line: RUN(bla bla bla); So i'm pretty sure the standard Class is saved within the plugin.

I'm not completly sure what you mean, but the default class of a tool is saved in the tool itself. So you have to backup your plugin folder. The one in your user folder (for the plug ins you made yourself) en the one in the apps folder (for the standard one of VW).

That's odd, i'm pretty sure it used to work, i've changed this at work long time ago... But that was still in version 12, so maybe it changed since then? Sorry to have caused you trouble Bill, that was never my intention.

Bill, the default sketchstyle is document bounded, so you have to change it in your template. Open your template, go to your resourcebrowser (I hope it's called like that), right click on your sketchstyle and choose "use sketchstyle as default". To make sure everybody knows what i'm talking about, it's this option: If your sketchstyle doesn't show up in the list, make a rectangle first, change it's sketchstyle in the OIP and then it will apear in the list. Then save that drawing as your template, that chould do the trick.

It should work normally. But make sure that they are on the same line, and that they have the same reference point.

Please, leave the symbols as they are, they are just perfect like they are, changing them will only cause problems... There's a logic behind them, and making them re-scalable or adjustable would go 100% against this logic, so please... No! But, instead of changing the symbols, NNA could maybe come up with an other sort of object, the Parametric Symbols? They can be somewhat the same as PIO's , but only much easier to make. For example: You draw something, you select it an convert it to a Parametric Symbol, so the same way as you make a Symbol, with the only difference that you can give it some Parameters, like scale factor, text, reals, booleans, Popups, Control Points... Then when you go inside that Symbol, you can start using those Parameters. For example, you can link the length of a line to a Real- or Dimension-Parameter, the diameter of an arc to an PopUp-Parameter, the visibility of a rectangle to a Boolean-Parameter, the origin of a text object to a Control Point-Parameter, the content of a text object to a Text-Parameter,.... That way you'll have the groups (easy and quick in making, adjustment and use), the symbols (perfect in repetitive things and they save in file size), the PIO's (quick in use, but not easy to make) and the Parametric Symbols (quick in use and quite quick to make them) Just a thought of course. But i'm not sure that NNA will be trilled to make something like this, it can cause that more and more people will just buy the basic version of VW and make their own "pio's"...

I think it has to do something about the ".", it needs to be a ",". Try this one, and see what you get in the message, if it's a ",", then you need to change it in your script: Procedure Tipo_e_Area; VAR Shape: HANDLE; Center,Area1,X,Y: REAL; Area,Comodo: STRING; n: INTEGER; BEGIN Shape := Nil; Shape:= FSActLayer; IF Shape <> NIL THEN BEGIN Area1:= HArea(Shape)/10000; Area:= Num2Str(2, Area1); message(Area); { n := Pos(',', Area); Delete(Area, n, 1); Insert('.', Area, n); } HCenter(Shape,X,Y); Comodo:= StrDialog('Nome do Comodo or Room name','Quarto'); IF NOT DidCancel THEN BEGIN PushAttrs; TextJust(2); TextVerticalAlign(2); TextSize(9); TextOrigin(X,Y); TextSize(12); FillPat(0); BeginText; ConCat(Comodo, Chr(13), Area, ' m2') EndText; PopAttrs; DSelectAll; END; END ELSE AlrtDialog('Select a solid 2D shape and try again.'); END; Run(Tipo_e_Area);

If you follow Ray's work around, you'll have 2 hatches, one colored one, and one grey. So now you can change the hatch by class. If you want the colored one, you set the colored one as your class hatch, if you want the grey one, you choose the grey one... You can not put the lines of hatch in a class or give it class attributes

SetRField asks for a STRING instead of a REAL, so you need to turn that REAL to a STRING. You can do that with Num2Str. So in your cause you could write it as: SetRField(h, 'Column', 'OA Height', Num2Str(0,Colz));

Jaap There is a minicad converter on vectorworks.be Just go to "Mijn Vectorworks" and then to "downloads", there you'll find at the end of the list a translator that will convert a minicad file to a Vectorworks file. That vectorworks file you then can export to a pdf with the VectorWorks viewer (also available on that same site). Athough i'm not very sure if you can export to PDF with the viewer...

well, not completly true, they speak about it in the VS Language Guide, in the chapter "Using VectorScript Plug-ins" -> "Plug-in Properties and Management" -> "Plug-in Options" - > " Plug-in Properties" But you have to know what you're looking for, otherwise you'll never find it, as a matter of fact, if Gerrit wouldn't have told me this, i wouldn't have know it either... So indeed, the manual could be better organised imo

You can already put tools in a default class. Go to the Vectorscript plugin module (or whatever it's called in English), select in the list the tool you want to edit and fill in the class in marked zone. When the class does not excist, it will be created in the document.

+1 it's posibble in other programs, so VW shouldn't stay behind imo.

You need to check this option (Is it called "Stack Layers"? sorry don't know the English translation of it).