<?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: Wall/Slab junction.Same module, different heights in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Wall-Slab-junction-Same-module-different-heights/m-p/287048#M148427</link>
    <description>For the record: IMHO, this is a good example when to resort to Solid Element Operation (SEO) because you're resolving a condition that only occurs locally. There will be no detectable time delay penalty unless you really abuse the SEOs.</description>
    <pubDate>Tue, 30 May 2017 18:32:24 GMT</pubDate>
    <dc:creator>matjashka</dc:creator>
    <dc:date>2017-05-30T18:32:24Z</dc:date>
    <item>
      <title>Wall/Slab junction.Same module, different heights</title>
      <link>https://community.graphisoft.com/t5/Modeling/Wall-Slab-junction-Same-module-different-heights/m-p/287047#M148426</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I have a little issue with the height of walls which are part of an apartment module. &lt;BR /&gt;
Wall positions and heights are all identical except for a few occasions where additional structural beams are required which require the wall height to be reduced. &lt;BR /&gt;
Is there a way for the beam to cut out the extra wall height (see image). I don't want to start using display order (send to back/bring to front) to deal with this as it is not a permanent solution. I'd also rather not use solid element operations but might have to as a last resort.&lt;/T&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Archicadquestion.jpg" style="width: 999px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/10838iF8C6A10A7C53FD5C/image-size/large?v=v2&amp;amp;px=999" role="button" title="Archicadquestion.jpg" alt="Archicadquestion.jpg" /&gt;&lt;/span&gt;</description>
      <pubDate>Wed, 24 May 2023 06:31:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Wall-Slab-junction-Same-module-different-heights/m-p/287047#M148426</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-24T06:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: Wall/Slab junction.Same module, different heights</title>
      <link>https://community.graphisoft.com/t5/Modeling/Wall-Slab-junction-Same-module-different-heights/m-p/287048#M148427</link>
      <description>For the record: IMHO, this is a good example when to resort to Solid Element Operation (SEO) because you're resolving a condition that only occurs locally. There will be no detectable time delay penalty unless you really abuse the SEOs.</description>
      <pubDate>Tue, 30 May 2017 18:32:24 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Wall-Slab-junction-Same-module-different-heights/m-p/287048#M148427</guid>
      <dc:creator>matjashka</dc:creator>
      <dc:date>2017-05-30T18:32:24Z</dc:date>
    </item>
  </channel>
</rss>

