Pat Stanford

Ok, so just use a large boarder size with really big margins. Format Page for 11 x 17. Set the Border size to 17 x 23 Outside Dimension Set the Margins to 3.5 inches on all four sides. This should give you a really big gap between the outside "page" line and the rest of the border objects. If that is still not enough to not print on the 24 x 36, make the outside dimensions and the margins even bigger.

So EVERY node that creates an object or objects in a network will result in an group as the output of the network? Even if the object created was only to be used as source geometry for further operations??? If I add a GROUP node at the end and take the output of the Polygon node and the Duplicate Object node into the objs input, I get a single group out. That group contains a single group and that group contains 5 polygons. If I add Group node to just the Duplicate Object node, I get a group/group/4 polygons which is closer to what I would expect. There is something here that is not making sense to me at all. What am I missing? What do I need to do to get a single group with 4 polygons, the original and the 3 duplicates?

What I am seeing here is that the output of the network is two groups. One group is a single polygon, probably the one generated by the original Regular Polygon node. The other has three polygons, the same number as specified to the into the Duplicate Object node. I think the question or bug is why is a network with a single open output generating two groups?

The file you posted does not have an object named "bli". without that object, the Contours command can't run. What kind of object were you using for bli? Can you post a file that is complete with everything you are trying to do?

It is called a wrapper. Select any nodes in the network, right click and choose Create Marionette Wrapper. You can use this wrapped node in other networks just as you would a default node. Just make sure you name the inputs and outputs you want to use so they can be seen outside the wrapped object. You can also take a Wrapper one step further. Right click on it and you can then Convert to Object Node. This makes an object that is effectively a PIO that will automatically update when you change the parameters without having to manually run the script. All of the named inputs are shown in the OIP. The output is a VW Marionette Object in the drawing. You can have multiple instance of Marionette Objects just as you can have multiples of the same PIO in a drawing. If you need them to be resources, you can Create Symbol. If you want it to revert back to a Marionette Object upon placement in the drawing, check the Convert to PIO checkbox when you Create Symbol.

I have looked at this a couple of times over the years. I do not think there is any way to turn it off. It is just part of the PIO to draw the outside border. So who is going to submit the wish to have the option to not draw the outside border on the Sheet Border object?

If you don't need the dimension marks, here is another way to do this in pure Marionette without requiring a custom node.

Several ways. One would be to name the object you want to use as the path. Then in the Marionette network you could access the object by name and use it as you want. Another way would be to make a Control Group. This is kind of like the path and profile objects in an extrude along path. You can access/edit this by right clicking on the Marionettte Object. I think you are stuck with the name option if you want to do it with a Marionette Network or Wrapper Node instead of with a Marionette Object. See the following thread for more information about Control Groups https://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Main=43136&Number=215710#Post215710

I'm not certain, but I think when I tried to convert a network or node to and Object without already having the Control Geometry there, I got an error due to an undefined handle. The Object was then basically missing. The only way I could edit it was with Enter Group and only because it was the only object in the drawing. Am I missing something or is that the way it works?

How about a work around? Oversize the page dimensions just a little so that the "page" rectangle is outside of the actual printable area? You may also need to play with the Border Margins to get things lined up as you like them. You will have to look at it when you draw, but it won't show up on prints or PDFs.

I think what you are looking for is the check box in the OIP titled: Use as Title Block Only. Or maybe I am not understanding you. Is what you want to have the inside box and the Horizontal and Vertical Zones show, but just not the outside box?

Also look at Get3DCntr, Get3DInfo (watch the data return order), and Get3DOrientation.

Control Geometry is similar to the Path Object and Profile Object in an extrude along path. Using this allows you to "manually" change the geometry used to create a Marionette Object. There is only a single Control Geometry object allowed, but that object can be a group, so you can effectively put as many different objects into an Object as you want. Run the Control Geometry input through a Contents node and you will get a list of the items in the stacking order they were in the group. Run that through a List Explode node and you can then access each individual object in the Control Geometry group to use as you see fit. To put the initial Control Geometery into the object select the group containing the control objects and the network, right click on the network and Convert to Object Node. If you right click on a Marionette Object you get an option to Edit Control Geometry. If you double click on an Object you get a dialog box asking if you want to Edit the Control Geometry or the Script.

You need to use some extra criteria to differentiate between the different areas. They could be on separate layers, different classes, or you could even give each planting area a name in the Data tab of the OIP. There are probably other items that would work as well. Add an extra column to the schedule with a formula to display the differentiating Criteria (=L for layer, =C for class, =N for name) Next select a row in the database and then drag a SUM tile to the column header for the column you just added. You many need to use an additional SUM tile on column that specifies the plant types to act as an "UNSUM" and get multiple rows for each area. Let us know if you need more info.

For now, Python is basically a wrapper around the existing Vectorscript calls. For the "fairly" simple things that an individual Marionette node should do, you can probably think in VS and write it almost line for line as Python. For me the hardest part is making sure that the capitalization is EXACT and remembering the white space matters. In Python the VS Begin and End statements you use to define the scope are replaced by having everything in the block have the same indentation.

VE-95553

Maybe this is not exactly the same thing, but I think that we need the ability to set an object's class to "From Parent" That way an object inside a group or symbol definition will automatically take on the same class that the Group or Symbol Instance has. If the attributes of the contained objects are set to By Class, then the contained objects would use whatever class the container (Parent) is in. I think this would solve a lot of the multiple class visibility issues that we see and make it much easier to use class attributes on objects such as notes. Consider a large block arrow with text inside. You might want the block and the text to be different colors to indicate different types of objects. Currently the best way to do this is to have multiple object each with defined colors. With the From Parent option, you could set instances of the parent to the red class, the green class and the blue class. each individual instance would then use the attributes for that class.

If you really want to control the section cut height and don't need the 2D functionality of Top/Plan mode is to cut a section viewport of an elevation viewport. 1. Create a viewport from an elevation view on a sheet layer (you may be able to do this with a design layer viewport, but I have never tried) 2. Cut a section viewport across the elevation viewport at whatever height you need.

Looks good. The attribution is fine. Glad you were able to work it out for yourself. That is the best way to learn.

Try this: Procedure SelectShorterLines; {If the first selected object in the drawing is a line} {this script gets the length of that line and selects all} {other lines in the drawing that have a shorter length.} {September 11, 2015} {February 13, 2012} {© 2015, Pat Stanford pat@coviana.com} {© 2012, Coviana, Inc - Pat Stanford pat@coviana.com} {Licensed under the GNU Lesser General Public License} Var H1 :Handle; OLength :Real; Procedure DoIt(H2:Handle); Begin If HLength(H2)End; Begin If GetType(FSActLayer)=2 then Begin OLength:=HLength(FSActLayer); DSelectAll; ForEachObject(DoIt,((T=LINE))); End Else AlrtDialog('First Selected Object Must Be A Line.'); End; Run(SelectShorterLines); I changed the comparison in the DoIt routine from = to <. I also added a DSelectAll function in the main routine so you will only have lines shorter that the original selected at the end, not the shorter lines plus the original line.

There was a thread recently where we "discovered" that the split tool can not be used to convert a closed poly to an open poly. The user was trying to use the split across just one "leg" of a poly and it was not working. If he drew completely across then it was fine. For your extrusion of multiple polys is something similar happening?

If you edit your workspace, there is a menu command called Custom Visibility in the Legacy folder. You can use this to automatically write scripts to show and hide objects based on whatever criteria you want. It was removed from the standard workspaces a few versions ago. And remember if you are using scripts to change visibility settings, the most important script of all is just a single line: SHOW(ALL); This will set the object visibility of all objects to visible. Usually does not do much good to hide objects if you can't get them back.

While the two fields hold the same data, they are truly separate fields. VW does not currently have a way to "link" fields together. Even if you could, based on the way the revision record is set up I don't think it would do what you want. The revision data is actually one big record with find names repeated 50 times with incremented numbers. So when you do the first revision the field you want would be something like revision.RevNum1. After the second one it would be something like revision.RevNum2. (I have not gone back and checked the actual record and field names. It would be relatively easy to write a script that would look through the regions record for the last non-blank revision number field and copy that data to the title block Rev field. But this script would still have to be run manually after every revision modification.

Sorry Mike, Active Only probably won't work. Unless the wall and all of the parts of the doors and windows are all in the same class, When you go to Active Only almost everything will disappear. Active Only is exactly that. Show the objects that are in the Active class. Any objects that have a different class but are "contained" by an object in the active class (think groups, symbols, walls, etc.) will not display.

What percentage of your time do you spend drawing? How large of drawings are you doing? Mostly 2D or lots of 3D? Rendering? OpenGL or Renderworks? How many renders do you typically do? How high of quality are you looking for from your renders? All of these questions and more need to go into the decision on what machine to buy. If you draw 75% of the time, the difference between the machine you asked about and the top end is $1/hour over 1 year. You will rarely be unhappy getting something faster.