Transferring a value from a variable to a lib part parameter (with SYMB_POS_FROM_SURVEY_POINT)

[Martin Jan Rosa]

Dear GDLers,

I am working on a library object that is similar to the Coordinate Dimensions object from the standard library. However, my goal is to have the X and Y coordinates relative to the Survey Point as a library element parameter, and thus be able to output them to a schedule as other library part parameters.

In the 2D script I work with the coordinates using SYMB_POS_FROM_SURVEY_POINT (plus some transformations due to our national practice - this is also the reason why I don't use the standard Survey Coordinate X,Y,Z property for listing in the schedule).

I'm struggling with how to get the value of such a variable into a parameter. The usual route via PARAMETERS doesn't work for me. At the same time, I can't use that SYMB_POS_FROM_SURVEY_POINT directly in the Parameter script (it pops up an error saying it's "project dependent", and I'm not actually surprised at the non-functionality here).

Can anyone think of a tip that might guide me a bit to the right solution?

Cheers,

Martin

[scottjm]

Based on the GDL reference guide the data of

SYMB_POS_FROM_SURVEY_POINT is not accessible by the parameter script, therefore it’s impossible to push that data back into a Parameter unfortunately.  

https://gdl.graphisoft.com/reference-guide/general-object-parameters

the only other way I can think to do it is to use 

SYMB_POS_X etc and enter the co-ordinates of your survey point in manually and does the offset calculation. 
This would mean you’d have to enter the survey point co-ordinates manually in every object though which would be possible risk for input errors. 

does the standard Archicad co-ordinate object have parameters you can schedule?

[Martin Jan Rosa]

Thank you for your reply, which confirms my concerns.

Unfortunately, the standard co-ordinate object does not have the necessary X/Y/Z parameters that could be shown in table.

[scottjm]

I’ve been lured down that dark path by GDL many times only to find out a certain global variable doesn’t work with the parameter script. It’s very frustrating.