topic Library Globals in Libraries & objects

Library Globals

Anonymous — Tue, 14 Sep 2010 15:33:44 GMT

Hopefully someone with more gdl/library knowledge will be able to help.

After updating to AC 14 I began having issues with my Library Globals not showing up in v.13 projects. I have since traced the issue and corrected it, the cause apparently being that I edited the "LibraryGlobals.gsm" in v.14. I replaced that .gsm with a previous version that was edited w v.13 and all seems to be ok now, but that leads to a more interesting question...

If a .gsm parts is edited in v.14 does it become unusable in a previous version of AC? or is it only parts such as Library Globals that are not truly independent parts?

Should I be keeping a v.13 Bim Server Library and a v.14 Bim Server Library?

Re: Library Globals

Barry Kelly — Wed, 15 Sep 2010 01:43:51 GMT

jbissaillon wrote:
If a .gsm parts is edited in v.14 does it become unusable in a previous version of AC?

Correct.
A library part edited in a particular version can only be read by that version or future versions.
So you either maintain a library for each version or do all your library part editing in the oldest version you want to use.
You will only need to edit library parts in the latest version if you want a particular new function - but make sure you keep the original library part to use in the older versions.

I script most of my parts in version 10 still but if there is a feture of a newer version I need to use I don't bother editing the part again in 13 or 14.
I just do the following.

if REQ("GDL_version")>=1.604 then !!VER13 and above
... script new commands here - ie Library Globals
endif

This way older versions will ignore the commands that it can't do.

Barry.

Re: Library Globals

Anonymous — Wed, 15 Sep 2010 12:29:05 GMT

Thanks Barry!

Re: Library Globals

Frank Beister — Wed, 15 Sep 2010 13:54:11 GMT

... script new commands here - ie Library Globals

In my experience you can't save an object with commands, which do not exist in the current AC version. Global parameters and runtime environment values of course, but not new commands.

I found only one trick to exclude the commands in a macro object, which is called depending von GDL version. The makro is written and saved in the upper version.