<?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 Layer management - INDEX question in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/Layer-management-INDEX-question/m-p/629179#M10872</link>
    <description>&lt;P&gt;Here is a topic that starts to be a nuisance.&lt;/P&gt;&lt;P&gt;Ever since I started working in depth with ArchiCAD, I functioned based on the observation that making new layers or importing new layers, will be a process that always places them at the end of the roster, independent of the gaps that are in the Index field. This is how some companies end up after multiple changes with indexes in the 800s... This never failed. I never was able to find a setting that could control that.&lt;/P&gt;&lt;P&gt;Unless, I wanted to append by index, this was a given.&lt;/P&gt;&lt;P&gt;I ran a quick test in 27 to verify this in a simple solo and a "hot-linked" instance and the results are the same.&lt;/P&gt;&lt;P&gt;However, I get people that tell me that when they make layers, theirs just simply go and fill the gap.&lt;/P&gt;&lt;P&gt;What is your experience? Am I going crazy here? (You don't have to answer this one...)&lt;/P&gt;&lt;P&gt;Here is how I made my quick test:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-08-29 at 8.31.12 AM.png" style="width: 768px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/75742i3C56294311EA0610/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2024-08-29 at 8.31.12 AM.png" alt="Screenshot 2024-08-29 at 8.31.12 AM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="grey"&gt;Operating system used: &lt;EM&gt;Mac Intel-based 16.6.1 Sonoma&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 29 Aug 2024 15:34:26 GMT</pubDate>
    <dc:creator>Lucian Laculeanu</dc:creator>
    <dc:date>2024-08-29T15:34:26Z</dc:date>
    <item>
      <title>Layer management - INDEX question</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Layer-management-INDEX-question/m-p/629179#M10872</link>
      <description>&lt;P&gt;Here is a topic that starts to be a nuisance.&lt;/P&gt;&lt;P&gt;Ever since I started working in depth with ArchiCAD, I functioned based on the observation that making new layers or importing new layers, will be a process that always places them at the end of the roster, independent of the gaps that are in the Index field. This is how some companies end up after multiple changes with indexes in the 800s... This never failed. I never was able to find a setting that could control that.&lt;/P&gt;&lt;P&gt;Unless, I wanted to append by index, this was a given.&lt;/P&gt;&lt;P&gt;I ran a quick test in 27 to verify this in a simple solo and a "hot-linked" instance and the results are the same.&lt;/P&gt;&lt;P&gt;However, I get people that tell me that when they make layers, theirs just simply go and fill the gap.&lt;/P&gt;&lt;P&gt;What is your experience? Am I going crazy here? (You don't have to answer this one...)&lt;/P&gt;&lt;P&gt;Here is how I made my quick test:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-08-29 at 8.31.12 AM.png" style="width: 768px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/75742i3C56294311EA0610/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2024-08-29 at 8.31.12 AM.png" alt="Screenshot 2024-08-29 at 8.31.12 AM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="grey"&gt;Operating system used: &lt;EM&gt;Mac Intel-based 16.6.1 Sonoma&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2024 15:34:26 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Layer-management-INDEX-question/m-p/629179#M10872</guid>
      <dc:creator>Lucian Laculeanu</dc:creator>
      <dc:date>2024-08-29T15:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: Layer management - INDEX question</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Layer-management-INDEX-question/m-p/629214#M10875</link>
      <description>&lt;P&gt;When placing a hotlink module or copying &amp;amp; pasting between files ...&lt;/P&gt;
&lt;P&gt;If the attribute number does not exist in the host file, then it will simply be created with the same attribute number as in the original file.&lt;/P&gt;
&lt;P&gt;If the attribute number is already used in the host file, but is for a different named attribute, then a new attribute will be created with the first available 'empty' attribute number.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If a user creates a new attribute, then it will become the highest attribute number + 1, it won't use the first available 'empty' attribute number.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Barry.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Aug 2024 02:07:40 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Layer-management-INDEX-question/m-p/629214#M10875</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2024-08-30T02:07:40Z</dc:date>
    </item>
    <item>
      <title>Re: Layer management - INDEX question</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Layer-management-INDEX-question/m-p/629673#M10886</link>
      <description>&lt;P&gt;I'll take that...&lt;/P&gt;</description>
      <pubDate>Tue, 03 Sep 2024 15:50:04 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Layer-management-INDEX-question/m-p/629673#M10886</guid>
      <dc:creator>Lucian Laculeanu</dc:creator>
      <dc:date>2024-09-03T15:50:04Z</dc:date>
    </item>
  </channel>
</rss>

