topic Re: PROFILE archicad 10 in Modeling

PROFILE archicad 10

Anonymous — Thu, 23 Nov 2006 15:07:06 GMT

Hi.
Using the hot linked module between two or more files when i change the shape of a profile in a file after the update the shape do not change .
When i copy an element from another file on the server automaticaly all the profiles of all the files appear in the list.
Please help
Marco

Re: PROFILE archicad 10

Anonymous — Thu, 23 Nov 2006 17:50:59 GMT

It appears that the revised profile attribute is not being read in the update. You can use Attribute Manager to update the profile.

Re: PROFILE archicad 10

TomWaltz — Thu, 23 Nov 2006 18:07:49 GMT

This has long been a complaint of mine, that attributes do not update between files that are hotlinked together.

Matthew is right, that the Attribute Manager is probably the best route to making them match.

This is particularly annoying in Teamwork projects!

Re: PROFILE archicad 10

Anonymous — Thu, 23 Nov 2006 18:44:37 GMT

TomWaltz wrote:
This has long been a complaint of mine, that attributes do not update between files that are hotlinked together.

Mine too. I wish that attributes could be externally referenced like libraries. Perhaps the LCF could provide the means to this.

Re: PROFILE archicad 10

Laszlo Nagy — Tue, 28 Nov 2006 09:50:36 GMT

I think this whole thing is because attributes are referred to by index number, but an attribute referred to by the same index number in two files may different definitions in those files. In such a case, the program always uses the definition in the host file.
If you change an attribute in a hotlinked file, that same attribute will not change in the host file into which it is hotlinked. You would have to change the attribute in that file, too.
This is true for Profiles, Fill Types, Line Types, etc. etc.

Re: PROFILE archicad 10

Ignacio Azpiazu — Tue, 11 Sep 2007 18:44:32 GMT

It is not only hotlinks. I have just copypasted into some file a profiled beam from some other file where I had stored the profile with its own name and non-template-overlapping ID.

The beam displays correctly in the destination file, but the attribute doesn't get 'stored' --I don't get the new profile in Profile Manager. In order to be able to select it in the destination file I need to import it through Attribute Manager.

This is not how fills, materials, etc. work. I wish I am missing something. Why would profiles have some ehm suckinessability specific to them?

AC 11 1040.