2004-06-21 10:13 PM
n = REQUEST("SYMB_POS_X", xorgn)Shouldnt the object get it's origin in the X axis relative to the model origin and place that numeric value in the parameter "xorgn"?
2004-06-22 12:47 AM
2004-06-22 05:31 PM
PARAMETERS x1 = SYMB_POS_Xbut for some reason I always get null values even when in plan.
2004-06-22 06:54 PM
Sean wrote:Try the following test in the 2D script:
I thought so, however, when I use it in conjunction with a print command in the 2D script, I keep getting a return of 0.
TEXT2 0, 0, SYMB_POS_X
Sean wrote:Using the PARAMETERS statement alone doesn't set the value of the variable. Try the following:
You would think that I could create a length parameter and assign that global value to it like so:PARAMETERS x1 = SYMB_POS_Xbut for some reason I always get null values even when in plan.
PARAMETERS x1 = SYMB_POS_X x1 = SYMB_POS_X
2004-06-22 11:27 PM
mark1 = STR("%0.16ffi",SYMB_POS_X) mark2 = STR("%0.16ffi",SYMB_POS_Y) mark = mark1 + "," + mark2 xorgnstr = mark1 yorgnstr = mark2This at least created the text in the plan view but it still does not place this information in the text parameters (xorgnstr, yorgnstr). I've done different things in the master, 2D and parameter scripts to no avail.
2004-06-23 02:32 AM
2004-06-23 08:26 PM
James wrote:BAH! That figures.
It's a bug. X~, Y~, and Z~ (SYMB_POS_X, _Y, _Z) all return zero in any context except the 2D and 3D window. That means, no reaction in the settings dialog, and no Listing X,Y positions of objects. They're 'working on it'.
2004-07-01 12:27 AM
2004-12-13 06:05 PM
Skywalker wrote:"Luke"
No, it's not a bug!
It's the feature
The way it works: create component, which contains SYMB_POS_X and then get it by lister
2009-06-10 07:48 PM