<?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: re-naming Layer Combinations causes missing views in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/re-naming-Layer-Combinations-causes-missing-views/m-p/203638#M29974</link>
    <description>&lt;BLOCKQUOTE&gt;Haneef wrote:&lt;BR /&gt;Should the layer setting in the view not update to reflect the re-naming.&lt;/BLOCKQUOTE&gt;

You would think so ... if ArchiCAD were truly a database... but unfortunately, layer combos and certain other attributes are stored by their name, not their index number and so renaming "breaks" view settings.&lt;BR /&gt;
&lt;BR /&gt;
I recommend that everyone have two "auditing" (error checking) interactive schedules at the top of their View Map to remind them to check each for errors before printing a project.&lt;BR /&gt;
&lt;BR /&gt;
One checks every View for any "Missing" combos, model view options, and other improper settings.  (Unfortunately, you cannot schedule all view settings - but these are the ones that get broken by renaming/etc.)&lt;BR /&gt;
&lt;BR /&gt;
The other checks placed Drawings to make sure that they all have the proper scale, zoom, pen set, title, etc.&lt;BR /&gt;
&lt;BR /&gt;
I'll attach my view scheme XML next, but here is a screenshot of where in Index Settings to Import the XML I'm posting.  (General note - this is how you export schedules from one project and import the schemes into another until your template stabilizes.)&lt;BR /&gt;
&lt;BR /&gt;
The advantage of opening an 'auditing' schedule such as this is that when things go 'missing', you can quickly find and correct the views since the schedule is interactive.&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Karl</description>
    <pubDate>Wed, 13 Apr 2011 15:48:33 GMT</pubDate>
    <dc:creator>Karl Ottenstein</dc:creator>
    <dc:date>2011-04-13T15:48:33Z</dc:date>
    <item>
      <title>re-naming Layer Combinations causes missing views</title>
      <link>https://community.graphisoft.com/t5/Documentation/re-naming-Layer-Combinations-causes-missing-views/m-p/203637#M29973</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;Not sure if I'm missing something.&lt;BR /&gt;It seems that if one renames a Layer Combination that was used by a certain view, it goes 'missing' in that view.&lt;BR /&gt;Should the layer setting in the view not update to reflect the re-naming.&lt;/DIV&gt;</description>
      <pubDate>Mon, 22 May 2023 21:28:36 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/re-naming-Layer-Combinations-causes-missing-views/m-p/203637#M29973</guid>
      <dc:creator>Haneef Tayob</dc:creator>
      <dc:date>2023-05-22T21:28:36Z</dc:date>
    </item>
    <item>
      <title>Re: re-naming Layer Combinations causes missing views</title>
      <link>https://community.graphisoft.com/t5/Documentation/re-naming-Layer-Combinations-causes-missing-views/m-p/203638#M29974</link>
      <description>&lt;BLOCKQUOTE&gt;Haneef wrote:&lt;BR /&gt;Should the layer setting in the view not update to reflect the re-naming.&lt;/BLOCKQUOTE&gt;

You would think so ... if ArchiCAD were truly a database... but unfortunately, layer combos and certain other attributes are stored by their name, not their index number and so renaming "breaks" view settings.&lt;BR /&gt;
&lt;BR /&gt;
I recommend that everyone have two "auditing" (error checking) interactive schedules at the top of their View Map to remind them to check each for errors before printing a project.&lt;BR /&gt;
&lt;BR /&gt;
One checks every View for any "Missing" combos, model view options, and other improper settings.  (Unfortunately, you cannot schedule all view settings - but these are the ones that get broken by renaming/etc.)&lt;BR /&gt;
&lt;BR /&gt;
The other checks placed Drawings to make sure that they all have the proper scale, zoom, pen set, title, etc.&lt;BR /&gt;
&lt;BR /&gt;
I'll attach my view scheme XML next, but here is a screenshot of where in Index Settings to Import the XML I'm posting.  (General note - this is how you export schedules from one project and import the schemes into another until your template stabilizes.)&lt;BR /&gt;
&lt;BR /&gt;
The advantage of opening an 'auditing' schedule such as this is that when things go 'missing', you can quickly find and correct the views since the schedule is interactive.&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Karl</description>
      <pubDate>Wed, 13 Apr 2011 15:48:33 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/re-naming-Layer-Combinations-causes-missing-views/m-p/203638#M29974</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2011-04-13T15:48:33Z</dc:date>
    </item>
    <item>
      <title>Re: re-naming Layer Combinations causes missing views</title>
      <link>https://community.graphisoft.com/t5/Documentation/re-naming-Layer-Combinations-causes-missing-views/m-p/203639#M29975</link>
      <description>Here's my personal view auditing scheme.  I'll rearrange the columns depending on what sort order I need to correct problems I find.  At the moment, it is sorted by view map.&lt;BR /&gt;
&lt;BR /&gt;
When having layer combo issues, you might put the combo field first so that it is sorted by that, grouping all 'missing' combo views together for easy recognition and correction.&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Karl</description>
      <pubDate>Wed, 13 Apr 2011 15:50:47 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/re-naming-Layer-Combinations-causes-missing-views/m-p/203639#M29975</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2011-04-13T15:50:47Z</dc:date>
    </item>
  </channel>
</rss>

