<?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: Teamwork, Reserving Elements, and HLMs in Teamwork &amp; BIMcloud</title>
    <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Teamwork-Reserving-Elements-and-HLMs/m-p/187975#M1702</link>
    <description>Thanks, Laszlo</description>
    <pubDate>Fri, 11 Jul 2014 17:31:46 GMT</pubDate>
    <dc:creator>Craig Bagley</dc:creator>
    <dc:date>2014-07-11T17:31:46Z</dc:date>
    <item>
      <title>Teamwork, Reserving Elements, and HLMs</title>
      <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Teamwork-Reserving-Elements-and-HLMs/m-p/187973#M1700</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;In my current TW project, reserving an element that is part of a hotlinked module reserves the entire instance of the module, even with "Suspend Groups" checked. So "My Workspace" shows any and all Project Regions containing elements from the hotlinked module.&lt;BR /&gt;
&lt;BR /&gt;
Can't seem to find an explanation of this behavior anywhere. Is this normal behavior?&lt;BR /&gt;
&lt;BR /&gt;
I'm using AC15, but even with the current Help Center, I can't find an explanation.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 11 Jul 2014 00:29:17 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Teamwork-Reserving-Elements-and-HLMs/m-p/187973#M1700</guid>
      <dc:creator>Craig Bagley</dc:creator>
      <dc:date>2014-07-11T00:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: Teamwork, Reserving Elements, and HLMs</title>
      <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Teamwork-Reserving-Elements-and-HLMs/m-p/187974#M1701</link>
      <description>Yes, I think it is normal because a Hotlinked Module is basically a big locked group. I guess the reason it reserves all elements of the HLM is because anything you do with them, you can only do it with every element of the HLM.</description>
      <pubDate>Fri, 11 Jul 2014 03:28:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Teamwork-Reserving-Elements-and-HLMs/m-p/187974#M1701</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2014-07-11T03:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: Teamwork, Reserving Elements, and HLMs</title>
      <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Teamwork-Reserving-Elements-and-HLMs/m-p/187975#M1702</link>
      <description>Thanks, Laszlo</description>
      <pubDate>Fri, 11 Jul 2014 17:31:46 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Teamwork-Reserving-Elements-and-HLMs/m-p/187975#M1702</guid>
      <dc:creator>Craig Bagley</dc:creator>
      <dc:date>2014-07-11T17:31:46Z</dc:date>
    </item>
  </channel>
</rss>

