Home › Forums › Problems and solutions in GDL › Parameter connections › Testing for D_iSlidingType in LibraryGlobals13 › Reply To: Testing for D_iSlidingType in LibraryGlobals13
Still doesn’t answer the question why the GS door worked though.
I am guessing the GS door knew to use the LibraryGlobals13 file for the 19 library and your doors would have been using the other one.
You will probably see two GDL options in your MVO dialogue.
I know when you CALL a macro by name it actually compiles the GUID into the script (although we only see the name).
Once saved you can rename the call macro file in your operating system and the object will still find the correct macro even though it is calling the old name.
So I am assuming the same is happening with the LIBRARYGLOBAL command – each was linked to the GUID for their respective macro file.
I may be wrong.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bit