<?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>idea Associated components family template en Revit Ideas</title>
    <link>https://forums.autodesk.com/t5/revit-ideas/associated-components-family-template/idi-p/9461512</link>
    <description>&lt;P&gt;Currently there are principle objects that are placed into a project, such as walls and doors, but there is no simple and adaptable container file that can hold ancillary items that are only required because of the presence of the principle object.&lt;/P&gt;&lt;P&gt;For instance:&lt;/P&gt;&lt;P&gt;Windows or doors require ancillary items such as lintels, flashings, trims, closers etc. Some approach this by hosting those items in the principle family, but this is not fundamently correct. Another approach is to have a separate 'generic' family containing ancillary objects which is manipulated manually or by dynamo / api but why should Architects have to jump through so many hoops? This goes against the original principles of Revit.&lt;/P&gt;&lt;P&gt;It would be good to have a family that can pull values from another family during placement and maintain that communication and respond to adjustments made to the principle object.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Apr 2020 08:40:58 GMT</pubDate>
    <dc:creator>paul_matthews</dc:creator>
    <dc:date>2020-04-22T08:40:58Z</dc:date>
    <item>
      <title>Associated components family template</title>
      <link>https://forums.autodesk.com/t5/revit-ideas/associated-components-family-template/idi-p/9461512</link>
      <description>&lt;P&gt;Currently there are principle objects that are placed into a project, such as walls and doors, but there is no simple and adaptable container file that can hold ancillary items that are only required because of the presence of the principle object.&lt;/P&gt;&lt;P&gt;For instance:&lt;/P&gt;&lt;P&gt;Windows or doors require ancillary items such as lintels, flashings, trims, closers etc. Some approach this by hosting those items in the principle family, but this is not fundamently correct. Another approach is to have a separate 'generic' family containing ancillary objects which is manipulated manually or by dynamo / api but why should Architects have to jump through so many hoops? This goes against the original principles of Revit.&lt;/P&gt;&lt;P&gt;It would be good to have a family that can pull values from another family during placement and maintain that communication and respond to adjustments made to the principle object.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Apr 2020 08:40:58 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-ideas/associated-components-family-template/idi-p/9461512</guid>
      <dc:creator>paul_matthews</dc:creator>
      <dc:date>2020-04-22T08:40:58Z</dc:date>
    </item>
  </channel>
</rss>

