LIBRARYGLOBAL for Door Minimum Spaces

[Anonymous]

Does anybody out there know how to get values from the default GS library globals?

I've been trying to scratch this out for over an hour. I just need to find out the value of the Model View Option for door minimum space.

Is there any decent documentation on this? The GDL Reference Manual and GDL Technical Standards are a bit too vague and cryptic for my tired mind at the moment.

ETA: This is for the US library. I don't know if it would be different for others (though I certainly hope not).

[Barry Kelly]

I don't know about any good documentation that will help but this might help explain it I hope.

What you need is this ...

success = LIBRARYGLOBAL ("LibraryGlobals13", "showBMinSpace", req_showBMinSpace)


Where "LibraryGlobals13" is the name of the macro that creates what you see in the MVO dialogue box.
It is a bit like the "Master_GDL" macros - you can have as many as you need so long as they are saved with the key words "LibraryGlobals" in the name.
Oddly enough the file in the version 16 AUS library is called "LibraryGlobals13" and not "LibraryGlobals16" - so not sure what the US library is like.

"showBMinSpace" is the name of the parameter that you want to get the value of.

req_showBMinSpace - is the parameter you want the returned value to go to.

the "success =" bit is just needed to avoid an error message.
The value of "success" will be 1 if it can find the parameter you are after and 0 if it can't.

Barry.

[Anonymous]

Thanks very much Barry!

I had it pretty close to what you describe except for quote marks around the parameter name and the req_showBMinSpace variable name.

The part and parameter names are the same in the US library. I'm guessing that's an international standard but since it could be anything I don't like to assume.

Oddly enough the file in the version 16 AUS library is called "LibraryGlobals13" and not "LibraryGlobals16"

I assume the part name is because the feature was introduced with AC13.

What I really don't understand is, if they are trying to give us more control and access to global variables and view options why not give us the information we need? Very frustrating.

...but thanks again for picking up the slack for them. Cheers.

[Anonymous]

One more thing just for the sake of completeness in case someone searches for this some time.

The target variable ("req_showBMinSpace" in Barry's example) can be named whatever you want within the standard limits for variable names.

[Jochen Suehlo]

Barry wrote:
It is a bit like the "Master_GDL" macros - you can have as many as you need so long as they are saved with the key words "LibraryGlobals" in the name.
Barry.

From my experience it is not necessary, to use the keyword "LibraryGlobals" in the name.
You have to choose the subtype "Library Global Settings" and name it whatever you like; the object should not been placeable as well.

Frank Beister has an example (open library globals) on www.opengdl.org

[Barry Kelly]

Joachim wrote:
From my experience it is not necessary, to use the keyword "LibraryGlobals" in the name.
You have to choose the subtype "Library Global Settings" and name it whatever you like; the object should not been placeable as well.

Correct.
It has been a long time since I have had to set any of this up.
Thanks for the clarification.
Barry.