_c_

I express a WISH to have associative hatch origin hooked to the carrier object and not only to the document's internal origin. A choice shoud be given among two modus: the present one (internal origin) and a new one to be defined (object origin and direction through a settable vector). The hatch origin should be editable on the object where it applies. The hatch origin should be editable with particular detail in walls, should be aware of cavities and be editable in the polygon representing them, cavity by cavity. This wish opens up a discussion about the details of how it should work. I think this is not the place or the time to discuss this. I realize this is a big modification in the application, but I am confident that this wish is taken into consideration. It is time to take it into consideration. Thank you, Orso

There are no such commands in the application, you must have them as plug-in commands from someone else. I suppose that "Toggle Layer Colors" operates the Document Preferences > Use Layer Colors. As script that would be: SetPref(11, NOT GetPref(11)); Probably "Toggle Line Weight" is simply toggling VectorWorks Preferences > Display > Use Line Thicknesss. As script that would be: SetPref(9, NOT GetPref(9)); Just open your plug-in Editor, find the scripts, enter their code and check if they more or less correspond. Stuff like that will unlikely be encrypted. Also check that the workspace you are using is the one where the scripts are loaded and those key shortcuts are defined. Both scripts might seem not to be operative, if you are not in the conditions to view their results.

* select the window * Attributes > pen style NOT by class * Attributes > pen thickness NOT by class

Kill me tenderly. I like the dongle. You can install legally the app anywhere you wish, you cannot use it anyway, if you don't have the preciousss. For vagabund workers like I am, is no bad advantage. orso

Just wait for being unhappy. You don't really have to start right now.

You can use this feature: references allow to override class attributes. From an open document needing to be updated to the new attributes set, create a reference to a file where * a layer exists with an object for each class. The class attributes of this document are the new ones. * the reference to this file has Update class definition = TRUE Please consider this feature carefully. It means that you can build a system of class attributes overrides allowing you to switch very fast from one attributes set to another. Ideally you'll want to save these files as standards, because they allow an easier access. They will be meant as reference-only files and as source for "New" class. Further, you should reference them from some of your templates, taking care to check the option Update Reference > Automatically during open: TRUE. This will grant that every new file is always up-to-date. Going bejond this, you can hook them to Wall style defaults, hatches defaults.... If you put up your architecture well, you'll have only to maintain few files, while all others follow. The drawback is that they need to be opened once, the children files referencing the standards, if you make some changes in the masters. I keep a folder with all aliases/links and simply give it a go whenever I made a change. Since I work mostly on Windows, I cannot enjoy AppleScript facilities there. * create a standard which you could name "Master Classes". This resides on the Standards folder. It includes a layer called something like "master classes layer". You must take care that all classes are represented by an object on this layer, without exception. Now we wish to have a document with the same classes, but different attributes. * duplicate the "Master Classes" file in the Standards folder, call it anything you please, for example "Children Classes 1". * Open it * rename the layer "child 1 classes layer". * modify your class attributes as you please. * create a reference to the previous "Master Classes" file, make sure to pick the "master classes layer", set Update Reference > Automatically during open: TRUE update class definition = FALSE This grants that the referenced file has the same classes of the master file, but the attributes are not overriden. Now, from your working files, do this experiment. * create a reference to "Master Classes" with: update class definition = TRUE All classes whose name exist in the document will be re-set to the attributes of "Master Classes". Do the same experiment changing the reference to the second Standard, "Children Classes 1". Now all classes changed in one click to a new attribute set, as stored in "Children Classes 1".

Additionally, you will find very comfortable to toggle the symbols insertion in walls on/off with the key "i" (if you didn't change this in Workspace Editor > Misc. Keys > Mode Groups > 2 ). * select a door or symbol in wall * press "i", you'll notice that the "Wall insertion mode" in the data bar disabled/enabled. If "Wall insertion mode" is enabled, you can take the symbols away from walls, if it is not, you can't. The last option might be more comfortable for precise positioning of your inserted symbols/plug-in objects. (sorry Pat, this wasn't REALLY meant as a reply to you, c)

The layer Z values are absolute in the current document. I don't know exactly how you built your roof, but some elements might cause it to seem to shift. After all you can always: * press key 2 (front view) while you are in the roof layer * check if this roof instance is really sitting on its Y = 0, * and even if it sits there, well, move it! Take the whole roof and do move it by the y needed. ciao, orso

You can set the roof's layer to more fitting Z (not confuse this with dZ) or you can modify the roof's value. This can be complex. Whatever you do, you'll like this command: * Go to the layer below your roof * Select the walls which are involved with your roof * AEC > Fit walls to roof. Select the proper layers in the dialog. It is one of my favorites. I guess your are almost there. You just need to experiment a little. It is really easy, actually. Let the application do math for you, always create new layers from "New", if you are in trouble. The whole model story is a layer's Z, dZ story. It isn't much, actually.

You should give manually a proper Z and dZ value to the layer where the Roof resides. The new layer created by the roof command is always one above the one you're in, in the stacking order, which has no direct influence on its height. Since you might have very specific values for your roof layer, this new layer has blank values. Mostly we use a layer that has already been prepared, where most likely other things reside. As to the roof modification, there is so much there to say. Please first go through the official documentation. The floor is placed with the AEC > create space command. Take care to select the walls first that will be forming your floor slab. You can also draw a polygon and do AEC > floor, which is much simpler. * select the walls * Create Polys form Walls > check Gross Area to TRUE, then you have a proper polygon. * AEC > floor Thickness = .35m, bottom Z = -.35m The Floor will be perhaps insufficient for the external terrain, there you might wish to explore the DTM facilities (AEC > Terrain)

Let's start from scratch. You'll probably understand the Model Setup better, if you go through this simple example before running the Model Setup command: * create a new document from a default fitting your needs. Let's say you pick Architect.sta. Pick one where the units will be OK for you: metrical. Pay attention that your units settings might now be mm, because of the template. You find the units setting relevant for this experiment in File > Document Settings > Units > General Display > Units: set meters or mm as you need, but pay attention that I am using now meters in this explanation. * The Navigation palette has many tabs, alt-click the "Layers" tab. The Organization Dialog appears. There you can view all layers and more. Let's speak now only about the layers. * You have only one layer, now. This layer (which is a floor for you), has: Z = 0 (height above an imaginary ground level) dZ = 0 (thickness of the floor, until the next floor) Set Z = 0.15m (this is your expressed wish for the ground floor) Set dZ = 2.4m + (thickness of the floor slab ). Let say your slab has .35m then the height dZ is 2.75m Now you have a ground floor with ceiling height 2.4m residing .15m above ground. We don't deal yet with the thickness of the floor slab, that would be the missing .35m that you need for creating a ceiling height (pavement and construction). * On the Organization Dialog select "New". A dialog appears, name the new layer how you please. A new layer (floor) will be created. If you look at it throughly, you'll notice that the new layers picks values relatively increasing from the previous: this new layer has now: Z = 2.9m dZ = 2.75m Let's now stop here for a moment. Exit the Organization dialog clickin on OK. * In the first layer draw some walls, like they would be enclosing a room, take care that their attribute "Link wall height to layer dZ" is ON. This you find in the Object Info Palette selecting the walls. Copy the walls, paste them in the second layer. * In the Navigation Palette > Layers you have two layers. Set the pull-down menu "Layer Options" to "Show Others". Make sure both layers are visible. * Select View > Stack Layers. Now you can view comfortably your model. Stack layers is meant for viewing, so to further work on the drawing you should disable it again. * Go to the last layer you created, select all walls * Select AEC > Create Roof... * A dialog for creating a roof appears. Set Roof Pitch to 30, check the radio button near it. If you want the roof to be in a new layer, set Layer > "New Layer" in the pop-up menu. A new dialog appears, name the new roof layer how you please. Confirm the dialog OK. Confirm the Roof Dialog with OK. There you have a roof, which you can further modify. It takes 2 minutes to set this up once you know how to. This is programmatically simplified and made project-wide compliant with the Model Setup command, which you'll probably enjoy later. I hope now you got the grip of how the VW model work. It is actually excellent. Fast, uncomplicated and efficient. You'll love it. orso

Less is more, Jan15.

Sure.

You can't. Simply set the jamb to a thin line. The error of not displaying a sectioned jamb is less visible than the error of a sectioned threshold.

111040167141163040152165163164040167157156144145162151156147040167150171040141162145040171157165040144157151156147040164150151163056

Robert, these are your users. Abusers. Not so easy.

Tick-Tock, Tick-Tock.. tick, tack, tick, tack...... [italian time]

command + A Safari > Services > TextWrangler > New Window With Selection command + A command + I > here you have all words just randomly removed 300 from the count because of html layout stuff. I am unable to count.

:crazy:

:sick: About 4000 words. About "none".

Make jamb depth larger than sash depth. It will fix the issue instantly. orso

Upgrading to VW 12 greatly pays off in terms of efficiency. My 2 cents (I am not selling the software, me user...) orso

I am borne venetian. I never heard of venetian drapes and blinds! But I'd solve things like this creating a texture and applying a nice bump. Then the drape object will give you the needed curves. ciao, orso

It works now, we don't have much viewer, two or three together and the whole thing goes down :grin:. It is a very nice article from Joel Sciamma about color access through VectorScript. Actually a disquisition about how come the colors indexes are swapped at certain positions. I hope you'll find it interesting. If you use VectorScript you will. orso

We are looking for a snapshot of the color palette from MiniCad 1 to be put on "colors" on vcor. Can anyone send me a screenshot? Raymond Mullin provided us a great collection of "historical" color palettes. We are missing the first one.... thank you orso