We value your input! Please participate in Archicad 28 Home Screen and Tooltips/Quick Tutorials survey
2022-10-11 08:54 AM
I want to create some wet area objects with additional hotspots for use on a slab penetration plan. I don't want to modify the standard Archicad library objects so I will to create a folder of renamed copies of the objects that I can then modify and add to an office library.
My concern is that I understand there are problems with saving objects as objects, and I don't want to create conflicts between my modified objects and the standard library parts. So a two-part question: why is it a problem to save an object as an object, and how should I save copies that I can modify without causing conflicts?
Solved! Go to Solution.
2022-10-11 09:26 AM
There is no problem saving an object as another object (select in plan and 'save as' library part > object) - if that is what you mean.
This will simply create a script that CALLs the original object.
You can then set new parameter defaults, but you can't amend the script of the original object without affecting all other original objects - I hope that makes sense.
If you want to keep the original GS object as it is, then open the script for it and 'Save As' with a new name in you office library.
This will give the new object a new GSID and will not interfere with the original GS object.
You can now amend the script and set default parameter values as you wish in the new object.
You will now have two completely separate (although similar) objects.
You will need to be a little careful with any CALLed macros, as it will CALL the macros from the GS library.
Fine if you don't need to amend those at all.
If you do, open them and 'Save As' with a new name in your office library as well and then amend the CALL commands in the object to CALL the new macro name.
Barry.
2022-10-11 09:26 AM
There is no problem saving an object as another object (select in plan and 'save as' library part > object) - if that is what you mean.
This will simply create a script that CALLs the original object.
You can then set new parameter defaults, but you can't amend the script of the original object without affecting all other original objects - I hope that makes sense.
If you want to keep the original GS object as it is, then open the script for it and 'Save As' with a new name in you office library.
This will give the new object a new GSID and will not interfere with the original GS object.
You can now amend the script and set default parameter values as you wish in the new object.
You will now have two completely separate (although similar) objects.
You will need to be a little careful with any CALLed macros, as it will CALL the macros from the GS library.
Fine if you don't need to amend those at all.
If you do, open them and 'Save As' with a new name in your office library as well and then amend the CALL commands in the object to CALL the new macro name.
Barry.
2022-10-11 09:29 AM
Thank you Barry, much appreciated!
2022-10-11 01:54 PM
You can also go to location where your copy of Archicad is located, you will find there a folder named something like Archicad 25 library. This folder contains your standard Archicad library parts. You can simply copy this folder (to keep as backup) or the content you are interested in to another location. Here you can select the objects, rename them and then load into your project. This is handy if you plan on altering large numer of objects and dont feel like going trough opeoning and saving each of them idividually.
2022-10-12 03:13 AM
Just be careful.
Re-naming an object file does not alter the GSID that the program uses to recognise the file.
If the GSID is not altered, you can not have then original and new objects loaded at the same time as they will be treated as duplicates.
Only opening the file and 'Save As' will change the GSID - or there is the LP_XMLConverter to work with many objects at once - this might be able to manipulate the GSID as well.
Barry.
2022-10-12 04:02 AM
This is the issue I have seen previously in old office libraries. I knew it was related to saving copies of objects but didn't know why that caused a problem and was therefore wasn't sure how to avoid it happening with this new project for the new library. Very helpful!
2022-10-12 08:56 AM
Thanks, wasnt aware of that.