topic Re: Custom Libraries to New AC Versions in Libraries & objects

Custom Libraries to New AC Versions

Anonymous — Mon, 13 Jun 2016 18:56:56 GMT

Hello everyone,
I am trying to get a consensus on the best strategy for moving custom object libraries from version to version.

Back in 2008 we had a colleague here in our office create a collection of custom library parts for our architecture firm. Whenever a new version of ArchiCAD came out, we went through the lengthy process of opening up each .gsm file in the new version of ArchiCAD, saving, and closing (not "saving as" so we keep the same GUID). In our eyes, this ensured that the object was compatible with the new version, so we weren't trying to insert a v17 object into a v18 project.

Have you had issues with older libraries in newer AC versions? What has been your strategy to bring these objects along over the years?

Have you encountered issues with newer Archicad versions and their ability to read old ArchiCAD objects?

Looking forward to hearing what you have to say!

Re: Custom Libraries to New AC Versions

Barry Kelly — Tue, 14 Jun 2016 01:18:59 GMT

We have a completely custom library and still have objects dating back to version 6.5 that work perfectly well.
Most of our object have been upgraded over time as we have needed to modify them but still there are many old ones.
In fact I still stript my objects in version 15 just to ensure they are still compatible back to that version.

The only problem I have had is with versions 19 and now 20 in that they have restricted or cancelled the use of some GLOBAL variables and REQUESTs in some scripts (master, parameter and property).
But simply saving in the new versions will not solve these changes - although you should get error messages stating there is a problem.

Barry.

Re: Custom Libraries to New AC Versions

Anonymous — Tue, 14 Jun 2016 10:15:55 GMT

Barry wrote:
you should get error messages stating there is a problem

This is a best logic behind library part transfers. Basically, if it ain't broken — don't fix it.

Library parts should work without any problem from version to version, short of above mentioned changes in Graphisoft's attitude toward GDL in general.

As a general rule, simpler GDL objects will work longer, more complex ones, especially those that rely on some sort of GDL hack, might go out of style rather quickly if the "hack" gets fixed in the new version of GDL.

Re: Custom Libraries to New AC Versions

Anonymous — Thu, 23 Jun 2016 15:56:13 GMT

Thank you both for your input! We are going through our library anyway and may do some coordinating with our GS contact to expand this conversation. Will touch base again with useful info if i get any.