<?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: Long Shot in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/Long-Shot/m-p/200647#M24868</link>
    <description>...other than the object ID!&lt;BR /&gt;
&lt;BR /&gt;
It seriously limits the scheduling capacity.&lt;BR /&gt;
&lt;BR /&gt;
I'm having to manually add a list of 'idenitcal' window numbers to one of the set and weed out the others from the schedule (via using the IFC type classification in the criteria - good thing I don't need to use it right now).  &lt;BR /&gt;
&lt;BR /&gt;
Not super user friendly.&lt;BR /&gt;
&lt;BR /&gt;
Also noticed that even if the windows are different in elevation (say one has an awning on the left of a fixed panel and the other is the mirror image - so the 3d views are different) so long as the other displayed parameters match, the schedule will treat it as 'identical'.  &lt;BR /&gt;
&lt;BR /&gt;
I'd call that dangerous.</description>
    <pubDate>Fri, 05 Oct 2012 05:15:00 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2012-10-05T05:15:00Z</dc:date>
    <item>
      <title>Long Shot</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Long-Shot/m-p/200645#M24866</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Was wondering why my identical windows were not appearing as a single entry and then it hit me.&lt;BR /&gt;
Since the zone reading is inconsistent and the zone number is part of the window number - I've entered the zone number manually into old user parameter number 5.  This of course makes the windows non-identical.&lt;BR /&gt;
&lt;BR /&gt;
So the question is - Is there a way of omitting a field from the 'identical' comparison?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 05 Oct 2012 02:35:31 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Long-Shot/m-p/200645#M24866</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-10-05T02:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: Long Shot</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Long-Shot/m-p/200646#M24867</link>
      <description>Only by not showing (scheduling) the field(s) that make them different.  Items in a schedule are only considered identical (for grouping) if all scheduled values are identical.</description>
      <pubDate>Fri, 05 Oct 2012 03:53:38 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Long-Shot/m-p/200646#M24867</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2012-10-05T03:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: Long Shot</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Long-Shot/m-p/200647#M24868</link>
      <description>...other than the object ID!&lt;BR /&gt;
&lt;BR /&gt;
It seriously limits the scheduling capacity.&lt;BR /&gt;
&lt;BR /&gt;
I'm having to manually add a list of 'idenitcal' window numbers to one of the set and weed out the others from the schedule (via using the IFC type classification in the criteria - good thing I don't need to use it right now).  &lt;BR /&gt;
&lt;BR /&gt;
Not super user friendly.&lt;BR /&gt;
&lt;BR /&gt;
Also noticed that even if the windows are different in elevation (say one has an awning on the left of a fixed panel and the other is the mirror image - so the 3d views are different) so long as the other displayed parameters match, the schedule will treat it as 'identical'.  &lt;BR /&gt;
&lt;BR /&gt;
I'd call that dangerous.</description>
      <pubDate>Fri, 05 Oct 2012 05:15:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Long-Shot/m-p/200647#M24868</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-10-05T05:15:00Z</dc:date>
    </item>
    <item>
      <title>Re: Long Shot</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Long-Shot/m-p/200648#M24869</link>
      <description>&lt;BLOCKQUOTE&gt;Angry wrote:&lt;BR /&gt;
Also noticed that even if the windows are different in elevation (say one has an awning on the left of a fixed panel and the other is the mirror image - so the 3d views are different) so long as the other displayed parameters match, the schedule will treat it as 'identical'.  &lt;BR /&gt;
&lt;BR /&gt;
I'd call that dangerous.&lt;/BLOCKQUOTE&gt;

That's when you need to add in a field for the window handing - I think GS call it "Orientation".&lt;BR /&gt;
Then because the fields show different information they will list separately.&lt;BR /&gt;
Barry.</description>
      <pubDate>Fri, 05 Oct 2012 06:51:36 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Long-Shot/m-p/200648#M24869</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2012-10-05T06:51:36Z</dc:date>
    </item>
  </channel>
</rss>

