Using SYMB_POS_X
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎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"?
I've been playing around with this global and havent had much sucess.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2004-06-22 12:47 AM
You don't need the Request function.
SYMB_POS_X is the global that contains the value you are looking for.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2004-06-22 05:31 PM
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.
Basically I want the object (in this case a beam) to report the coordinates in plan view of each corner.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎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
Central Innovation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2004-06-23 02:32 AM
I was trying to get my tree objects to list their locations with respect to a grid... works perfectly, except for those pesky zeroes! Waiting for the fix.
(Thanks to F. Beister who clued me in when I asked the same thing on GDL Talk last month.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎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'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2004-07-01 12:27 AM
It's the feature

The way it works: create component, which contains SYMB_POS_X and then get it by lister
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎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
I'm so frustrated in trying to get symbol positions to report in interactive schedules that I can't tell if your comment "..It's the feature..." is serious or sarcasm.
If it is serious, can you please explain a little more in detail how it works?
thanks,
Dan K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2009-06-10 07:48 PM
Trying to write a simple library part to send X,Y coordinates to a schedule.
I can get the coordinates to show up in plan view, but not in the schedule.
Has anybody discovered a work-around?