C. Andrew Dunning
-
Posts
1,179 -
Joined
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by C. Andrew Dunning
-
-
Nate -
You might be interested in reading http://techboard.vectorworks.net/ubbthreads/ubbthreads.php?ubb=showthreaded&Number=86857 or http://www.lightnetwork.com//?msg=24755.1 . Both threads discuss the question you're asking.
In a nutshell...I'm fully in the "Single Layer But Many Classes" camp. (I tend to work on a single Layer with 100+ Classes.) With few exceptions, I've yet to see compelling reasons to work a different way. In fact, for most entertainment applications, I find the "Multiple-Layer" approach to add comlexity that is unneeded and makes drawing much more difficult than it should be.
Please forgive me if I sound a bit dogmatic. This is my opinion - is what works best for me - and is what I believe would be a much easier approach to learn.
As to your question about symbols containing multiple Classes, most of mine take advantage of that:
- Truss Symbols are created with both complex and simple geometry - as well as rigging guides - each in different Classes. Different Class visibilities can be set depending on what I'm wanting to see in a given instance. Am I creating a rigging plot? Am I placing fixtures? Am I needing a quick/simple structure layout at a tiny scale? Etc.
- Some fixture Symbols have both complex and simple geometry and all have the different data elements in separate Classes, giving me different visibility options based on a particular need.
- All of my Symbols contain loci in their own Class, allowing me to display or hide reference points using a simple toggle script.
My $.02...somebody else's turn...
Regards -
-
Chris -
All is up and going. The link in my original message doesn't seem to work - but copy-and-pasting it does.
Thanks.
-
Good morning!
Over the years there have been multiple inquiries about the availability of Genie symbols. We now have a small Plug-In Object for VectorWorks that is an answer to that need. Called "StageLift," it is a hybrid object that builds lift models - and that allows the user to change a few parameters, like fork position, width, and height. Attached is a rendering of one of the models.
If you're interested in more info, we have a little posted at http://www.landrudesign.com/VWPlugIns.htm .
Thanks!
-
Would you consider adding the same functionality to polygons?
At this point, probably not. Your best approach for that is probably to use the "Convert To Lines" command and then run "Curtain From..." on the selected lines.
-
Not an issue - so don't worry about the screenshot. It IS a tool and IS behaving exactly how it should. It is just not a stand-alone tool.
I've now updated the brief instructions that come with these files to try to clarify installation.
-
And what I'm trying to say is that the tool (LandruCurtain) is not supposed to go on any tool palette. It is not written to be a stand-alone tool. It's sole purpose is to be called by "Curtain From..." If the menu command is working, then both things are, indeed, working as they should.
That help?
-
The tool works in VW 12.5 or newer - including 2008.
The only questions that I'd have have to do with how you went about installing and running the files. Did you put both in your Plug-Ins folder? Did you only add "Curtain From..." to your WorkSpace? Are you running that command on a selected arc or line? The only way I get invisible (non-existent) objects is if I try to run LandruCurtain by itself - which it was not created to do.
Does this hep at all?
-
You need to have added "Curtain From..." to one of the menus of your WorkSpace.
Once you've done that, select one of the arcs and click that menu item. If a dialog box pops up, click OK. "Curtain From..." will then insert a PIO, using the arc as a reference.
Make sense?
2 things:
1) "Curtain From..." will only work on lines and arcs.
2) If you downloaded the Zip file this morning (3/14/08), it contains updated code that will work on multiple objects at the same time.
-
Try the link again. The forum software included my punctuation in as part of the link. I've removed the period and all seems to be working.
-
Lee -
I have a tool that does what you're needing @ http://www.landrudesign.com/LandruCurtain.zip
Add both files in the Zip file to your Plug-Ins folder. Add "Curtain From..." to your favorite WorkSpace. Create an arc where you want your curtain to end up. (Knowing you're wanting a circle, create 2, 180? arcs. Select 1 and run "Curtain From...", then do the same w. the other. You'll end up w. 2 PIOs for which you'll be able to change settings, like pleat depth and width.
Let me know how that works out for you.
-
Greetings from Nashville!
We are incredibly pleased to announce the official release of VideoScreen 3!
The three notable changes are:
1) The VideoScreen Plug-In Object many of you have grown to love is now a suite of tools. The features have grown in recent years and, instead of a single tool getting bloated with even more features, we decided to stream-line things a little in terms of "specializing" functions. "VideoScreen 3", comprised of "VideoScreen 3 - Television" and "VideoScreen 3 - Projection" is the "suite" equivalent to what you've been using.
2) A huge addition to the VideoScreen family is "VideoScreen 3 - Blended." "...Blended" constructs edge-blended projection screens in your VectorWorks drawings. It places Hybrid projector models and aids in estimating projector spacing and image overlap. (Many of you have asked about this functionality and we hope it meets your needs...)
3) In a response to a request made by a few of you, image dimensions and lens information that is displayed in your VideoScreen models is now draggable, broadening your model text layout options.
For those of you who are already users, there are a few upgrade options. See http://www.landrudesign.com/VWPlugIns.htm for more information.
Please feel free to e-mail me if you have any questions!
-
Good morning!
In celebration of being able to post files, here is a simple PIO that places text in automatically-resizing boxes.
(This is in reply to the discussion a while ago about scripting that process...)
-
Rich -
VectorScript Forum:
Look for the general heading here of "Software Customization." There is a VectorScript section underneath that. (http://techboard.nemetschek.net/ubbthreads/ubbthreads.php?ubb=postlist&Board=13&page=1)
Locale of your script:
If you're running Windows, check "C:\Documents and Settings\C. Andrew Dunning\Application Data\Nemetschek\VectorWorks\12\Plug-ins" (where "C. Andrew Dunning" is your user name. Newly-created scripts will end up there.
If I were you, instead of trying to create a menu command w. the code I posted, I'd create a document-specific script. I think you'd find that a bit easier to manage if this is your first go-round w. scripting. To do that, click the bottom gray "play (arrow) button toward the top of the Resource Browser. Select "New Resource" and then "VectorScript..." Select the palette where you'd your script to live. Give the script a name in the next dialog. Once you've done that, an editor window opens up. Input the code there and click "OK." The script will then be ready to run from the palette you chose earlier.
Color Chart script:
I don't remember if that is a stock menu item or not. (Anyone else know?) If not, I have no idea where I got it. One of those things I've grown to take for granted over the years.
Good luck...
-
Rich -
A "9" gives you 41120, 41120, 42148. The values pop up in a message box.
Running the script is a matter of double-clicking it - either in a script palette or in the Resource Browser.
Scripts created from within VW can't be opened with Notepad. If you created yours using the Script Editor, you have to use that to edit them. If your script is drawing-specific (created from the Resource Browser), right-click on the script and choose "Edit."
As to a table of the numbers, I don't know of one. The closest thing is either the Utility command I mentioned or the Color Table in the VS Function Reference document - both of which will give you Color Index numbers (the latter if you're using stock colors).
-
Rich -
Run "Create Color Chart" (Under Tools...Utilities in the Standard 13/08 WorkSpace). A color chart will be created with numbers in the color squares. Create the following script:
----------------------------------------
PROCEDURE Color;
VAR
r,g,b :LONGINT;
BEGIN
ColorIndexToRGB (0,r,g,b);
Message ('Red: ',r,' Green: ',g,' Blue: ',b);
END;
RUN (Color);
---------------------------------------
Replace the "0" in the ColorIndexToRGB line with the number of the color you're wanting. That will give you the RGB values, which is what VectorScript is wanting.
Make sense?
-
Pete -
(Soap-box alert...)
There are two thing in your post that are reoccurring topics - both here and in occasional discussions:
1) Layers and Classes:
I strongly recommend you rethink the way you're using Design Layers and Classes. Having, for example, "Intelligent" and "Generic" Classes AND Design Layers will only serve to increase confusion - and the number of steps required as you create. Multiple Layers can be quite helpful if you're working on, let's say, multiple spaces in the same project (different floors for architects or different performance areas for entertainment lighting designers) but can also add an unneeded level of complexity. For example, let's say you're working on a corporate event in a convention center - and event that involves several rooms. You might separate your work across multiple drawing files, or you might simply create multiple Design Layers and organize your elements into multiple Classes within those Layers:
Design Layers:
Main Session Room
Overflow Room 1
Overflow Room 2
Breakout Room 1
Breakout Room 2
etc.
Classes:
Room-Room
Room-Softgoods
Staging-Stage
Staging-Scenery
Lighting-Flown-Conventional
Lighting-Flown-Intelligent
Lighting-Flown-Truss
Lighting-Ground-Conventional
Lighting-Ground-Intelligent
Lighting-Ground-Truss
etc.
This way, your Class structure for each Design Layer is the same - but with no "purpose overlap" between Classes and Design Layers. Also, within a given space, changing views is much easier than if you had "same-space" elements in multiple Design Layers.
I've also seen lighting designers use a similar approach for designs for repertory productions.
2) Multiple Classes in Groups and Symbols:
Assigning separate Classes to the "sub-components" of Groups and Symbols (which are, themselves, assigned to Classes) is extremely useful. For example, a piece of entertainment truss might be in a Class called "Flown-Truss." The truss might be comprised of "Simple" and "Complex" geometry - allowing you to display truss as a simple box or as a collection of the chords, gusset plates, lacing, and rigging guidelines.
I know I'll be publicly ridiculed by my brethren for my comments, but this is the way I've found things to work best for me...
-
Thanks. I had been looking at the wrong VS reference document on my HDD - and neither of the on-line VS resources have any info (that I could find) on the new calls.
I'll have to do a little tinkering now to learn what the different variables do...
-
To make it possible to create these objects without having to worry about the aspect ratio (that changes when the coordinate system is rotated), 3 new calls were created: RectangleN, RRectangleN, and OvalN. These allow you to specify the rotation of the object, and then the bounding box of the object within that rotation.
Where can we get more info on these calls - what their syntax and variables are and how they funtion relative to, let's say Rect?
Thanks!
-
DWorks -
Makes sense. I hadn't thought of that (though several of my symbols do contain grouped elements).
The thing I'd tried to do (and gave up) was having certain lines within symbols change color (color only - not fill, pattern, or line style) based on which Class on which the symbols are placed. I have symbols that are used in different ways (in different Classes) and differentiating their purpose/Class at-a-glance using color would be a great thing...
Regards -
-
And more evidence of why I should think before typing...
Most of the elements in my symbols are already created in different classes. I use class visibility to control which of those elements are hidden or shown. There just isn't a way to control the graphical attributes of those things based on which Class in which a given symbol is placed.
I guess this is one of those "can't have my cake and eat it too..." things.
-
I'm referring to an outline feature like we have in a word processor where the subclasses would be indented from the parent class.
Ahhh... Makes total sense. Great idea.
-
boxjoint -
Would you care to explain what you mean by "the ability to show hierarchical lists"? Curious...
As to what DWorks was saying about the ability to adjust graphical attributes based on Class assignment, I love the concept but the vast majority of my work is symbol-based (the symbols need to remain symbols when placed) and, as far as I know, geometry within symbols cannot change attributes on a "per-instance" basis. Perhaps something for the Wish List...
-
I wonder if you would be willing to post a new topic explaining how you keep them all straight? How do you have your classes organized? What sort of naming convention do you use?quote]
I've taken advantage of 2 things in VW's handling of Class order:
1) I use numbers to group Classes of similar general function.
2) I use VW's Class name tree system to subdivide those functions.
That way, my Classes always show up in a specific order, regardless of what alphabet letter starts a given Class' name.
For example, "5" is a general division for stage lighting elements. ""Flown" and "Ground" are where those elements are placed.
A snippet from my Class list:
5 Flown-Conventional
5 Flown-Intelligent
5 Flown-Truss-Main
5 Ground-Intellig.
5 Ground-Convent.
5 Ground-Truss
Make sense?
-
Ion -
I've named most of my VPs. To get a given VP's handle I use GetObject (which looks for the name).
As to knowing what VP will display a given object, I don't know a way to do that - if that's even possible, aside from polling for Class visibilities.
Drawing organization
in Entertainment
Posted
A few thoughts:
Michael is quite right; it is a matter of taste. He is also right in that stacking order is much easier using Layers.
A curiousity question, Michael: How do you handle lighting a model and rendering? Do you use Layer Linking?
As to opacity, in 2008, individual objects now have an opacity setting in the Attributes palette.
As to "Z" values, in my approach that is on an object-by-object basis. It is extremely rare for me to have a design in which all of the flown elements are at the same height and the floor elements at the same height.