<?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: Weird Fill in Pocket Door in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166450#M22091</link>
    <description>Thanks Mathew and Jared, I will try your solutions.</description>
    <pubDate>Fri, 08 Jan 2010 01:48:32 GMT</pubDate>
    <dc:creator>Srinivas</dc:creator>
    <dc:date>2010-01-08T01:48:32Z</dc:date>
    <item>
      <title>Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166446#M22087</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hi there,&lt;BR /&gt;
&lt;BR /&gt;
I tried unsuccessfully to remove the fill in the pocket door (please see attached image for reference) I tried changing the fills in the Floor plan symbol but with no  luck, currently I am using a patch to cover this up, but sometimes when I send the drawings back to my client the patch object is sent back by the wall and this weird fill pops up, do anyone have a idea on how to fix this?&lt;BR /&gt;
&lt;BR /&gt;
Thanks in advance.&lt;/T&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="2010-01-07_Pocket_Door_Fill_Problem.png" style="width: 999px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/14022i2FC5AFF32A251C45/image-size/large?v=v2&amp;amp;px=999" role="button" title="2010-01-07_Pocket_Door_Fill_Problem.png" alt="2010-01-07_Pocket_Door_Fill_Problem.png" /&gt;&lt;/span&gt;</description>
      <pubDate>Wed, 24 May 2023 08:56:07 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166446#M22087</guid>
      <dc:creator>Srinivas</dc:creator>
      <dc:date>2023-05-24T08:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166447#M22088</link>
      <description>Deleting the fill from the file in my case "Pavement 16" is fixing the problem, but any thoughts on this would be helpful as i believe this is a long standing problem, at least for me.</description>
      <pubDate>Thu, 07 Jan 2010 12:40:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166447#M22088</guid>
      <dc:creator>Srinivas</dc:creator>
      <dc:date>2010-01-07T12:40:29Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166448#M22089</link>
      <description>Sounds like an index number problem. Over time with additions and deletions to the fill attributes the index numbers can get jumbled. This has been a long standing problem but a really tricky one to fix globally at this point.&lt;BR /&gt;
&lt;BR /&gt;
The better solution to deleting the fill is to replace it with the one you want. This is a bit tricky itself though since Attribute Manager doesn't allow direct editing of index numbers.</description>
      <pubDate>Thu, 07 Jan 2010 16:40:52 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166448#M22089</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-01-07T16:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166449#M22090</link>
      <description>To get around this problem, if the bad fill is #35, I delete the fill, then create dummy fills until the next empty fill is #35.  Make or duplicate a nice empty fill.  Delete all the dummies and you're good to go.  Once you have the right fill in one file copy it to all your others (or your template) via the attribute manager.  I've had to do this a few times.  Oh and if the index number is super high, see if you can find another file (AC template for instance) that has no holes in its fill list.  Delete the number you need, create the new fill, and copy into your file via the attribute manager.&lt;BR /&gt;
&lt;BR /&gt;
If you ever have trouble finding the screwy fill in the first place, just explode the pocket door/wall and select the now independent fill.&lt;BR /&gt;
&lt;BR /&gt;
Just deleting the fill and leaving the index number empty will probably create errors.</description>
      <pubDate>Thu, 07 Jan 2010 19:41:39 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166449#M22090</guid>
      <dc:creator>JaredBanks</dc:creator>
      <dc:date>2010-01-07T19:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166450#M22091</link>
      <description>Thanks Mathew and Jared, I will try your solutions.</description>
      <pubDate>Fri, 08 Jan 2010 01:48:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166450#M22091</guid>
      <dc:creator>Srinivas</dc:creator>
      <dc:date>2010-01-08T01:48:32Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166451#M22092</link>
      <description>Alternatively If you open up the library part of the sliding door, you should be able to change the patio stone fill to Air Space or whichever one you want.&lt;BR /&gt;
Save as a new version if you don't want to overwrite the standard library part.&lt;BR /&gt;
&lt;BR /&gt;
The advantage to doing this is that it will allow the patio stone fill, if called by other library parts in the file to not be messed up.</description>
      <pubDate>Fri, 08 Jan 2010 17:36:53 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166451#M22092</guid>
      <dc:creator>Erika Epstein</dc:creator>
      <dc:date>2010-01-08T17:36:53Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166452#M22093</link>
      <description>A much nicer solution!  And a good way to ease into tweaking and building library parts.</description>
      <pubDate>Fri, 08 Jan 2010 17:48:27 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166452#M22093</guid>
      <dc:creator>JaredBanks</dc:creator>
      <dc:date>2010-01-08T17:48:27Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166453#M22094</link>
      <description>Yes, we know about this bug. Embarrassingly, it is is regression bug in AC13. It will be fixed in the next Library Update.&lt;BR /&gt;
&lt;BR /&gt;
Sorry for the inconvenience!</description>
      <pubDate>Thu, 14 Jan 2010 15:18:09 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166453#M22094</guid>
      <dc:creator>ztaskai</dc:creator>
      <dc:date>2010-01-14T15:18:09Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166454#M22095</link>
      <description>Thanks Zsolt.</description>
      <pubDate>Fri, 15 Jan 2010 04:42:39 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166454#M22095</guid>
      <dc:creator>Srinivas</dc:creator>
      <dc:date>2010-01-15T04:42:39Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166455#M22096</link>
      <description>We investigated the issue. In fact this fill appears with the USA library in case you use a different attribute set than the one of the USA template. To overcome this, we introduced a parameter for this fill so that you can fit your object to your template. The Update Library is being tested; it will be out soon.&lt;BR /&gt;
&lt;BR /&gt;
Regards,</description>
      <pubDate>Fri, 22 Jan 2010 08:55:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166455#M22096</guid>
      <dc:creator>ztaskai</dc:creator>
      <dc:date>2010-01-22T08:55:21Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166456#M22097</link>
      <description>&lt;BLOCKQUOTE&gt;ztaskai wrote:&lt;BR /&gt;We investigated the issue. In fact this fill appears with the USA library in case you use a different attribute set than the one of the USA template. To overcome this, we introduced a parameter for this fill so that you can fit your object to your template. The Update Library is being tested; it will be out soon.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;/BLOCKQUOTE&gt;

Aloha Ztaskai,&lt;BR /&gt;
Is there any fix for the ArchiCAD 11 library D1 Pocket 11 door?&lt;BR /&gt;
Mahalo,&lt;BR /&gt;
John</description>
      <pubDate>Tue, 08 Jun 2010 19:11:18 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166456#M22097</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-06-08T19:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166457#M22098</link>
      <description>Hi John,&lt;BR /&gt;
&lt;BR /&gt;
Sorry, you have to live with the solutions from Matthew and from Jared in AC11. It's time to upgrade;)&lt;BR /&gt;
&lt;BR /&gt;
Regards,</description>
      <pubDate>Wed, 23 Jun 2010 17:22:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166457#M22098</guid>
      <dc:creator>ztaskai</dc:creator>
      <dc:date>2010-06-23T17:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166458#M22099</link>
      <description>&lt;BLOCKQUOTE&gt;ztaskai wrote:&lt;BR /&gt;Hi John,&lt;BR /&gt;
&lt;BR /&gt;
Sorry, you have to live with the solutions from Matthew and from Jared in AC11. It's time to upgrade;)&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;/BLOCKQUOTE&gt;

ztaska,&lt;BR /&gt;
Your approach to encouraging me to continue to use Archicad missed it's mark.  Why would we be encouraged to continue to pay more for a product that didn't work in the first place.  &lt;BR /&gt;
We might be more encouraged to upgrade if we got an apology for the broken program components that were delivered with version 11 (and other previous versions) and possibly a discount on the upgrade. &lt;BR /&gt;
&lt;BR /&gt;
I recommend that you spend your time fixing the bugs in the software and let someone more adept at customer service deal with sales and other customer satisfaction issues.  If an automobile or appliance manufacturer delivered a car or appliance with broken components they would be obligated to repair the parts.  It would be great if Graphisoft and other software manufacturers took a similar approach.&lt;BR /&gt;
&lt;BR /&gt;
In the meantime we are all grateful to Matthew, Jared and the other forum participants who are able to offer real world solutions to the problems that we encounter as you develop the software.&lt;BR /&gt;
John</description>
      <pubDate>Wed, 23 Jun 2010 22:54:26 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166458#M22099</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-06-23T22:54:26Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166459#M22100</link>
      <description>uff !! i was getting excited about the participation of GS !!  thanks god these guys have a good training in the beating dept during beta testing  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_biggrin.gif" style="display : inline;" /&gt;  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_biggrin.gif" style="display : inline;" /&gt;</description>
      <pubDate>Thu, 24 Jun 2010 02:12:47 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166459#M22100</guid>
      <dc:creator>Rakela Raul</dc:creator>
      <dc:date>2010-06-24T02:12:47Z</dc:date>
    </item>
    <item>
      <title>Re: Weird Fill in Pocket Door</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166460#M22101</link>
      <description>&lt;BLOCKQUOTE&gt;johncassel wrote:&lt;BR /&gt;...&lt;BR /&gt;
We might be more encouraged to upgrade if we got an apology for the broken program components that were delivered with version 11 (and other previous versions) and possibly a discount on the upgrade. &lt;BR /&gt;
&lt;BR /&gt;
I recommend that you spend your time fixing the bugs in the software and let someone more adept at customer service deal with sales and other customer satisfaction issues. ...&lt;/BLOCKQUOTE&gt;

Hi John,&lt;BR /&gt;
&lt;BR /&gt;
You are right in many ways. First of all, I shouldn't have encouraged you to upgrade, that's not my job. Second, my job really is to fix the bugs and make necessary developments - and to help users to find their ways with our current solutions. Third, Graphisoft could streamline the library update workflow a lot. Fourth, I owe you an apology regarding the quality of the 11 library. I truly hope we are doing better with our current work.&lt;BR /&gt;
&lt;BR /&gt;
We put a lot of effort into building and maintaining channels to collect user feedback and we try to fix the issues as technology and resources allow us. Naturally, we have to set up priorities for this job - which may put some user issues on a longer hold.&lt;BR /&gt;
&lt;BR /&gt;
I'm sorry, I made you mad. I'll think again before posting in the future.&lt;BR /&gt;
&lt;BR /&gt;
Best regards,</description>
      <pubDate>Wed, 07 Jul 2010 13:26:40 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Weird-Fill-in-Pocket-Door/m-p/166460#M22101</guid>
      <dc:creator>ztaskai</dc:creator>
      <dc:date>2010-07-07T13:26:40Z</dc:date>
    </item>
  </channel>
</rss>

