klinzey
-
Posts
2,550 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by klinzey
-
-
In general plug-ins are only forward compatible. You may find a few versions that are compatible only because the plug-in format did not change between versions.
As for compiler directives there are now a few available in 2012 so you can have conditional code run depending on the version. It's only going to work in 2012 and later so it will not do anyone much good now but in the future you will be able to conditionally exclude new 2013 code so that they will compile in 2012.
- IF directive ? This directive will define beginning of a block of code. It will contain a logical statement that will be evaluated. If the evaluation results in false, the following code until the ENDIF directive (or the end of the file) will be skipped by the compiler; If the evaluation results is true ? the code will be compiled; - ENDIF directive ? This directive will define the end of a conditional block of code; the corresponding end directive of an ?if? directive, should be inside the same include file. - DEFINE directive ? This directive will allow defining named values to be used in the IF directive conditions; this named variable is valid from the moment of definition until the end of the script or until it is undefined. - UNDEF directive ? Removes a named variable defined previously.
-
You need to create a rectangular plug-in object.
In the Plug-in editor when you click NEW select "Rectangular Object" rather than Point Object.
You will get 2 default parameters LineLength and BoxWidth which will control the length and with. You can access them just like any other parameter.
Unfortunately you can not change a Point Object to a Rectangular Object Plug-in.
-
As far as I know they are useless at this point.
They were originally designed to force obsolete functions and reserved names to cause a compile error.
Obsolete functions will now cause a VS warning if you have Stop on VS warnings turned on.
The last version I think they were functional was Vectorworks 8.
-
cvdub,
Check the symbol that is is use in your Label Legend. Select the symbol and choose fit to objects. You want to check to see that size of the selections looks correct and that there is nothing making the symbol look taller or wider than you expect.
As for moving the labels, do you see the blue handles over each label when the lighting device is selected? If the handles are not there you probably have Interactive Scaling disabled. To enable it activate the 2D selection tool and click the 2nd button in the mode bar.
-
Are you using stmbols from the 2012 libary and placed in 2012?
The 2012 symbols have a locus point placed in the combined multi-circuit symbol to indicate the roration point for the entire multi-circuit unit.
-
Which version are you using. Multi-circut units did not have the ability to rotate till 2012.
-
In the OIP of the lighting device there is a check box for "Set 3D Orientation". When that is check you will see 2 more parameters, X Rotation and Y Rotation. These two parameters along with the normal 2D rotation will allow you to orient the lighting device in 3D.
Normally hybrid objects can not have a 3D rotation so the lighting device has to create the rotation with these parameters.
-
That has been fixed in 2012.
It is the shutter plane. In 2012 if there are no shutter cuts the shutter cut plane is not drawn.
-
The locus for the emitter and the hing point are the same.
You need tr turn off "Draw Beam" because it blocks the rendered light. The file you posted did not have the default instrument texture applied to the symbol geometry. Try this one.
-
The locus point needs to be a X=0 Y=0 Z (only the Z value matters).
You need to apply a non shadow casting texture (for example the default instrument texture) to the 3D geometry in the symbol. This will allow the light to be inside of the geometry but still project.
-
If you encounter this message you should contact your local distributor.
Steve, please contact jalmansa@vectorworks.net.
-
Carl,
There were a lot of changes between v11.5 and 2011 in Vectorworks and Vectorscript. Several Vectorscript calls from v11 are not obsolete and no longer work in 2011. Also the Vectorworks file extension changed from .mcd to .vwx so any script that access external Vectorworks files will no longer be able to find or use the old .mcd files.
If you an give us the exact error message we may be able to help you out a little more.
-
The Key To Instrumentation is just a simple group. When it is created it is created with the document default text attributes. If you want to edit anything about the Key to Instrumentation just enter the group and change the text attributes.
-
Grant,
Nemetschek Vectorworks do most of our webinars using GoToWebinar\GoToMeeting.
If you are unavailable at the time of the webinar you should register anyway. Typically (but not always) everyone that registers gets a follow-up email with a recording of the session. Unfortunately if you are not viewing it live you don't get the opportunity to have your questions answered by the presenters. I'm not involved with this webinar so I don't know if there will be a recording of this one.
-
1994 should be a MiniCAD 5 (or 4) file so you need to find someone who has VectorWorks 8.0 or MiniCAD 7 in order to open it in a modern version of Vectorworks.
http://www.ozcad.com.au/support/faq.php
For really old files there is a stand alone translation utility for the Mac that you can try.
http://www.nemetschek.net/downloads/fundamentals/archived_downloads.php
-
I think there is something wrong with the GetWSCellNumberFormat call. I'm not seeing it return the values for the Leader and the Trailer. I'll enter it as a bug and get someone to take a look at it.
-
Steve,
This was a problem with Vectorworks 2012 that was resolved in 2012 sp2.
If you are using 2012sp2 and still having the problem please let us know.
-
Do you have some accessories? VW and LW handle accessories differently and the message is probably about those accessories not being updated by LW.
The automatic data exchange in LW5 is much better.
-
No, It's only valid inside the dialog handler.
-
No. GoTo is just about it.
In reality you should structure the code so that is is in an If Then Else statement after the dialog is finished.
If RunLayoutDialog = 1 then
Do Stuff
else
Do Nothing
-
2: would be the event of the "Cancel" Button but you really want to check the return value from RunLayoutDialog call outside of the dialog handler.
If it's not 1 then the user canceled or closed the dialog without hitting the OK button.
There are typically 3 default IDs used by the dialog.
1: OK Button
2: Cancel Button
3: Help Box
so your first control should be 4.
-
You should have access to the standard 255 of the classic Vectorworks color palette if you want to pick a color by index.
New colors will be generated with indexes greater than 255.
The good thing about this is that the first 255 colors will always be the same color from the Vectorworks color palette, previously if the user changed the color palette you would not know what color you would get using the index.
You can use ColorIndexToRGBN and RGBToColorIndexN if you need to find or create a color.
-
There have been a lot of changes since 2010. Check the attributes of the video screen and make sure they are all the same. One bay be set to have a black fill or use attributes or textures by class and causing it to render black.
-
The event seating looks for other objects placed by the event planning commands to use as a look to point. If none of those objects exists it places the look to point close to the center of the seating layout.
From there you can grab the control point and move it to where you need it. The simplest option is to snap it to the midpoint of what you want to be the front of the seating area.
It's impossible for the command to determine where the front of the seating is without finding some other object.
If you want to place the look to point when you are creating the seating area use the create seating layout command.
Modifying the Object to manipulate the variable?
in Vectorscript
Posted
You can change the "Alternative Name" (aka display name) but the actual parameter names can not be changed.