topic Re: libraries reload when updating modules in Libraries & objects

libraries reload when updating modules

Anonymous — Sat, 31 Oct 2009 03:56:32 GMT

when updating modules, AC13 wants to reload every library. this was not the case in AC12. any suggestions as to how this can be avoided?

Re: libraries reload when updating modules

Anonymous — Thu, 05 Nov 2009 22:42:33 GMT

I believe it is checking if you have any new objects in the embedded library of your module. If it has, it will add it to your library of the main project.

I don't think you can stop it.

Re: libraries reload when updating modules

Anonymous — Fri, 06 Nov 2009 04:44:12 GMT

disapointing, i didn't sign up for embedded libraries!
come on GS ninjas, we can put a man on the moon, but we can't update modules without reloading all libraries?

Re: libraries reload when updating modules

Lipi — Mon, 25 Jan 2010 14:11:07 GMT

It is utterly annoying and time consuming!
We are fixing about 25 modules, just changing the room layout, and every time we have to wait for all the libraries to load. It takes up a lot of time.
I also miss the "update this module" option in the right click menu on the floorplan, it was there in AC 11. Now we have to go through the manager. Grrr! Too much unnecessary clicking and reloading alltogether. Waste of time.

Re: libraries reload when updating modules

Anonymous — Mon, 25 Jan 2010 20:02:04 GMT

As long as you do not use the embedded library the process will be much faster! You can use a project library just in the old days. Only downside is that when you use a project library and Teamwork 2.0, AC will need to download the project library each time a change is made.

Re: libraries reload when updating modules

andrewzarb — Mon, 01 Nov 2010 05:52:50 GMT

ArchiCAD should not embed library parts in modules (.mod files).

It makes no sense.

The result of the current behaviour is that library parts are duplicated as many times as there are modules.

The result is that the ArchiCAD file reads the library part from an inserted hotlinked module instead of its own embedded part and therefore that library part does not get updated.

Re: libraries reload when updating modules

Anonymous — Thu, 12 Apr 2012 07:31:52 GMT

Did GS ever solve this problem? Still using AC13 and my problem lies when I edit stairs (actually, ramps made by the stair object) and when it embeds it to the module file, the old instance of the ramp persists in the file where the module is hotlinked. The workaround I have done is that to save a new stair (or ramp) with a different name. Although now I have a bunch of unused stairs.