Global variable for a "User origin"

[Anonymous]

Whether there is a global variable for a "User origin"?
There is a need(requirement) to use it in a library part.

[Anonymous]

There is none as far as I know. It is an interesting idea though. What do you need it for?

You are aware of SYMB_POS_X etc. I assume. This is relative to the project origin of course.

[Anonymous]

The problem consists that in ArchiCAD there is no opportunity to add a new pattern in the tool "Level Dimension". In Russia other standard for the image of the "Level Dimension". The state control of check of the design documentation demand to correct the images of the "Level Dimension" made by means ArchiCAD. Therefore the Russian architects working in ArchiCAD use a library part.
The library part uses global parameter SYMB_POS_Y.
If the drawing of a section is moved concerning the global beginning of coordinates it is necessary to bring in updating of this displacement.
It tires. It is better to use "User origin".

Interlocutors can rebuke: "Do not move sections and Use PlotMaker".
I shall answer: "I Deny any infringement of freedom of action".

[Anonymous]

You could create a library part that either sets some of the GLOB_USER variables or writes out a text file for its local origin. The other parts could then use these values. The text file is probably more reliable but perhaps a bit trickier to do. I am always a little nervous about reassigning the user globals since it is impossible to know what other parts may be trying to use them and I have had trouble in the past getting the values to update automatically.

[Anonymous]

You could create a library part that either sets some of the GLOB_USER variables or writes out a text file for its local origin.

I have no knowledge of how to use GLOB_USER. My unique manual it " GDL Reference Manual ". And in it there is no example how to use GLOB_USER.
Excuse, I have not understood, that was meant under " text file ". Tåêñòîâûé a file with expansion ".gdl"? If yes, and in this case I do not know as it it is possible to use.

I am always a little nervous about reassigning the user globals since it is impossible to know what other parts may be trying to use them and I have had trouble in the past getting the values to update automatically.

If I have correctly understood you, I have variant how to avoid automatic updating of a library part.
We admit, that there are global parameters for " User Origin ". We shall name one of them as "GLOB_USER_ORIGIN_Y".
Then I could, solve a problem(task). Externally it would look the same as in the tool " Level Dimension ".
Sketch of the script:
The new command is added: a name - "new_name", type - the text, the description - "beginning of the sizes"
Values "new_name" " Project Zero ", " User Origin "
IF GLOB_PAR_NAME "new_name" AND new_name = " User Origin " THEN correction=GLOB_USER_ORIGIN_Y

The parameter "correction" has taken value of coordinates on a Y-axis from GLOB_USER_ORIGIN_Y. Now "correction" it can be used together with "SYMB_POS_Y." "correction" any more will not change the value even if " User origin " will move to a new place.