<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Attribute Manager - Materials in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62154#M13225</link>
    <description>Somehow related: how should one handle composite names as they evolve over time? &lt;BR /&gt;
&lt;BR /&gt;
After several years of working pretty much on my own with my own fairly-fine-tuned system, I am now working as part of a team where composite definitions have been evolving over time, appearing during the process in different files and projects (sometimes it is the composite dimensions and fills that change a bit, sometimes it is pens only). &lt;BR /&gt;
The problem is that when you import attributes or get a module or copy-paste an object from another file that has a 'different' composite by the same name you end up getting, for example, '4 in gyp' and '4 in gyp (1)'. Which is very upsetting and disconcerting. You don't get a warning asking if you want to replace etc. &lt;BR /&gt;
&lt;BR /&gt;
Starting fresh from templates and attribute files keeps you safe with new stuff. But should one also add a date or version to the composite name in order to avoid this type of problem when reusing old stuff?</description>
    <pubDate>Thu, 18 Nov 2004 07:28:05 GMT</pubDate>
    <dc:creator>Ignacio Azpiazu</dc:creator>
    <dc:date>2004-11-18T07:28:05Z</dc:date>
    <item>
      <title>Attribute Manager - Materials</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62152#M13223</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Hi,&lt;BR /&gt;
&lt;BR /&gt;
is it a bug or why can't I download Material texture settings from another file? I get only the other settings for material, not the file settings..  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_question.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
/Tobias&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 26 May 2023 13:30:15 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62152#M13223</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-26T13:30:15Z</dc:date>
    </item>
    <item>
      <title>Re: Attribute Manager - Materials</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62153#M13224</link>
      <description>I found a solution. &lt;BR /&gt;
&lt;BR /&gt;
Open original file : save as *.aat file&lt;BR /&gt;
Open new file and import *.aat file and then it works.&lt;BR /&gt;
&lt;BR /&gt;
/Tobias</description>
      <pubDate>Wed, 17 Nov 2004 12:35:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62153#M13224</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2004-11-17T12:35:00Z</dc:date>
    </item>
    <item>
      <title>Re: Attribute Manager - Materials</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62154#M13225</link>
      <description>Somehow related: how should one handle composite names as they evolve over time? &lt;BR /&gt;
&lt;BR /&gt;
After several years of working pretty much on my own with my own fairly-fine-tuned system, I am now working as part of a team where composite definitions have been evolving over time, appearing during the process in different files and projects (sometimes it is the composite dimensions and fills that change a bit, sometimes it is pens only). &lt;BR /&gt;
The problem is that when you import attributes or get a module or copy-paste an object from another file that has a 'different' composite by the same name you end up getting, for example, '4 in gyp' and '4 in gyp (1)'. Which is very upsetting and disconcerting. You don't get a warning asking if you want to replace etc. &lt;BR /&gt;
&lt;BR /&gt;
Starting fresh from templates and attribute files keeps you safe with new stuff. But should one also add a date or version to the composite name in order to avoid this type of problem when reusing old stuff?</description>
      <pubDate>Thu, 18 Nov 2004 07:28:05 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62154#M13225</guid>
      <dc:creator>Ignacio Azpiazu</dc:creator>
      <dc:date>2004-11-18T07:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: Attribute Manager - Materials</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62155#M13226</link>
      <description>&lt;BLOCKQUOTE&gt;Ignacio wrote:&lt;BR /&gt;Somehow related: how should one handle composite names as they evolve over time? &lt;BR /&gt;
&lt;BR /&gt;
After several years of working pretty much on my own with my own fairly-fine-tuned system, I am now working as part of a team where composite definitions have been evolving over time, appearing during the process in different files and projects (sometimes it is the composite dimensions and fills that change a bit, sometimes it is pens only). &lt;BR /&gt;
The problem is that when you import attributes or get a module or copy-paste an object from another file that has a 'different' composite by the same name you end up getting, for example, '4 in gyp' and '4 in gyp (1)'. Which is very upsetting and disconcerting. You don't get a warning asking if you want to keep the old, replace with the new, or rename the new. &lt;BR /&gt;
&lt;BR /&gt;
Starting fresh from templates and attribute files keeps you safe with new stuff. But should one also add a date or version to the composite name in order to avoid this type of problem when reusing old stuff?&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Thu, 18 Nov 2004 07:30:45 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62155#M13226</guid>
      <dc:creator>Ignacio Azpiazu</dc:creator>
      <dc:date>2004-11-18T07:30:45Z</dc:date>
    </item>
    <item>
      <title>Re: Attribute Manager - Materials</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62156#M13227</link>
      <description>&lt;BLOCKQUOTE&gt;Ignacio wrote:&lt;BR /&gt;
Starting fresh from templates and attribute files keeps you safe with new stuff. But should one also add a date or version to the composite name in order to avoid this type of problem when reusing old stuff?&lt;/BLOCKQUOTE&gt;

My problem was that when I made my template file for AC9 all texture settings disappear and I don't want to start from scratch too do a new template when I use AC9 default material settings. But that problem is solved.  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_lol.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
But I'm agree with your post. Maybe a possibility too write longer composite names than it is today?  Today we can't write complete definition in composite name. &lt;BR /&gt;
&lt;BR /&gt;
Hope you understand my sometimes bad english.&lt;BR /&gt;
&lt;BR /&gt;
/Tobias</description>
      <pubDate>Thu, 18 Nov 2004 08:12:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62156#M13227</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2004-11-18T08:12:03Z</dc:date>
    </item>
    <item>
      <title>Re: Attribute Manager - Materials</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62157#M13228</link>
      <description>&lt;BLOCKQUOTE&gt;The problem is that when you import attributes or get a module or copy-paste an object from another file that has a 'different' composite by the same name you end up getting, for example, '4 in gyp' and '4 in gyp (1)'. Which is very upsetting and disconcerting. You don't get a warning asking if you want to replace etc.&lt;/BLOCKQUOTE&gt; &lt;BR /&gt;
 &lt;BR /&gt;
Couldn't this be avoided by having a set of .aat's on the company's server? If loading the composite's full .aat when starting up a new project (from a company template) everybody will have the same sets. If a new composite or an existing one needs to be adjusted, give it a new name + export/update the servers .aat so that the rest of your co-workers can up load the new composite. &lt;BR /&gt;
Also, could you a more specific system of giving (both new and old) composites names?  This way it will be easier to define similar composites that f ex only have a slight difference in thickness of one material ...</description>
      <pubDate>Thu, 18 Nov 2004 08:14:53 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Attribute-Manager-Materials/m-p/62157#M13228</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2004-11-18T08:14:53Z</dc:date>
    </item>
  </channel>
</rss>

