GUID

[vfrontiers]

Is it something I'm doing, or is it inherent in the system.

I've got an old part created some years back. Yesterday, I wanted to update it and SAVE as an AC12 object. All works just fine until the next time I open the file.

The old part AND the new part have the SAME GUID... so every instance of the NEW part that I placed (with new features) is now replaced by the OLD part and are missing all the new features.

These particular objects are actually LABELS, so I can't use the REPLACE w/ PARAMETERS feature of regular objects.

Anyone?

[Barry Kelly]

Yep - the label reverts back to the original when following Duane's instructions.
Even when I swap it for an existing label created in an earlier version.

However I tried it for a second time
Auto-lable with Duane's object, opened it and save it with another new name.
Then swapped one label for this second new object and another for the first new object.
Saved the file, closed and re-opened.
The lable swapped for the second saved label changed back but the other swapped for the first saved object stayed as it should have.

There is obviously a problem that needs to be fixed but it looks like it may be a little inconsistent.

I'm not sure if this helps or just makes it more complicated.

Barry.

[Barbara Sommer]

We have verified Duane's steps to replicate this problem and had the same experience as described. Our developers will fix this bug as soon as possible.
A workaround is to reassociate the wall with the new label.
So to untag the usage of labels within the wall selection settings, then reset the default for associative wall-labels and finally retag the usage of labels within the wall selection settings.

Sorry everybody for the inconvenience.

[vfrontiers]

Barbara,

Thanks for the reply. I did re-associate the labels yesterday and all seems to be working..

Thanks again!

[Ralph Wessel]

Barbara wrote:
We have verified Duane's steps to replicate this problem and had the same experience as described. Our developers will fix this bug as soon as possible.

This bug has been visible in the ArchiCAD API since ArchiCAD 11. If you change the lib part associated with an API_ObjectType and save with ACAPI_Element_Change, everything appears to work perfectly. The updated object is illustrated correctly in 2D and 3D, you can edit parameters, and you can duplicate it by dragging or copy/paste. However, if you save and reopen, all the objects (even the copies) will have reverted to the previous object. The only work-around was (through the API) to delete the original object and create a new one in its place.

When you implement this fix, can you also check this behaviour through the API too?

[Barbara Sommer]

We are fixing this bug in version 11 as well.

[Laura Yanoviak]

Barbara wrote:
We are fixing this bug in version 11 as well.

REALLY? So there will be another hotfix for AC11 at some point?

[Laszlo Nagy]

Yes, it seems like there will be. Barbara in another thread mentioned that there will be a new AC11 hotfix:

http://archicad-talk.graphisoft.com/viewtopic.php?p=136791&highlight=#136791

[Laura Yanoviak]

laszlonagy wrote:
Yes, it seems like there will be. Barbara in another thread mentioned that there will be a new AC11 hotfix:

Wow -- thanks Laszlo.