<?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: Model View Sets in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74294#M12050</link>
    <description>Sure.  Of course, even the "Export to XML" option is a big improvement over AC9 behavior.  MVO's have a similar function to Layer Combinations -- and I'm all for consistency...</description>
    <pubDate>Thu, 14 Jun 2007 23:27:15 GMT</pubDate>
    <dc:creator>Laura Yanoviak</dc:creator>
    <dc:date>2007-06-14T23:27:15Z</dc:date>
    <item>
      <title>Model View Sets</title>
      <link>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74290#M12046</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;Model view sets are very essential to the project file it self, my question is will there ever be the feature implemented within attribute manager to be able to transfer model view sets just as we do with composites, pens etc. Does anyone have any feedback?&lt;/DIV&gt;</description>
      <pubDate>Thu, 18 May 2023 22:19:38 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74290#M12046</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-18T22:19:38Z</dc:date>
    </item>
    <item>
      <title>Re: Model View Sets</title>
      <link>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74291#M12047</link>
      <description>So, when you say "View Sets" do you mean view settings, like a saved combination of:  Layer Combination, Scale, and Model View Option???  Or are you referring just to the Model View Option Settings?  in which case you can export to an XML file and import into another file.</description>
      <pubDate>Thu, 14 Jun 2007 21:08:04 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74291#M12047</guid>
      <dc:creator>Laura Yanoviak</dc:creator>
      <dc:date>2007-06-14T21:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: Model View Sets</title>
      <link>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74292#M12048</link>
      <description>&lt;BLOCKQUOTE&gt;DavidCSinohui wrote:&lt;BR /&gt;Model view sets are very essential to the project file it self, my question is will there ever be the feature implemented within attribute manager to be able to transfer model view sets just as we do with composites, pens etc.  Does anyone have any feedback?&lt;/BLOCKQUOTE&gt;
very difficult, of course, to import view settings when the viewport may or may not exist in the first place, no?&lt;BR /&gt;
&lt;BR /&gt;
i somewhat agree though . . . it would be nice to be able to populate the view map with complete view structures from other files. i guess this is where you really need to establish a template and start all jobs from it: pre-placed viewpoints, views and pre-placed on drawings on layouts.&lt;BR /&gt;
&lt;BR /&gt;
beware though: 'establishing a template' is not as simple as it sounds  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_wink.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
if you were talking about MVOs (model view option combinations), then as laura says, you can simply export them - albeit one-by-one - to an XML file and re-import into your new file . . .&lt;BR /&gt;
&lt;BR /&gt;
~/archiben</description>
      <pubDate>Thu, 14 Jun 2007 22:13:45 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74292#M12048</guid>
      <dc:creator>__archiben</dc:creator>
      <dc:date>2007-06-14T22:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: Model View Sets</title>
      <link>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74293#M12049</link>
      <description>MVO - it seems to me everything else is in attribute manager and very easy to transfer while not having to go in and out exporting and importing just a wishful thought that Im throwing out there to see if any agree that if MVO was implemented in the Attribute manager would this make you AC life a bit easier?</description>
      <pubDate>Thu, 14 Jun 2007 22:59:20 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74293#M12049</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-06-14T22:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: Model View Sets</title>
      <link>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74294#M12050</link>
      <description>Sure.  Of course, even the "Export to XML" option is a big improvement over AC9 behavior.  MVO's have a similar function to Layer Combinations -- and I'm all for consistency...</description>
      <pubDate>Thu, 14 Jun 2007 23:27:15 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Model-View-Sets/m-p/74294#M12050</guid>
      <dc:creator>Laura Yanoviak</dc:creator>
      <dc:date>2007-06-14T23:27:15Z</dc:date>
    </item>
  </channel>
</rss>

