<?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: Poorly written GDL Part Libraries in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33541#M36628</link>
    <description>&lt;BLOCKQUOTE&gt;Karl wrote:&lt;BR /&gt;I was thinking more in terms of my friend Tom Waltz who said that the AC library was too limited for his company ... but did not say how or why.  And others...&lt;/BLOCKQUOTE&gt;

OK, since Karl is being so nice, I'll elaborate: &lt;BR /&gt;
(OK, Karl is ALWAYS nice to everyone, I'm the one who's a jerk all the time)&lt;BR /&gt;
&lt;BR /&gt;
Keep in mind, many of these were decided in early 2003 when we first bought Archicad, and were on Archicad 8.0, but I think many of the same issues still apply. I should also mention that I have tinkered with almost every object we ever bought from anyone if they did not work as expected. I consider ObjectsOnline to be a toolbox where I can buy parts faster/easier than I can make them myself, not final products. If CADImage had not provided locked scripts, I probably would have been altering them as well. I am a tinkerer and a programmer at heart, and do not expect everyone to share my strangeness in this respect. I enjoy GDL programming, and have been fortunate to find myself in a position where I can do a lot of it for a demanding staff who wants to push the liimits.&lt;BR /&gt;
&lt;BR /&gt;
For the record, with the exception of my Stairmaker complaints, I have created objects to answer every complaint here.&lt;BR /&gt;
&lt;BR /&gt;
Default settings. I felt that the object library should have defaults that can be user-set like anything else. If you want your objects to have a certain pen, linetype, font, text size, line type, or detail level, you should be able to set that for all objects. All the ideas of favorites or modules are really just workarounds for that the Libraries should be able to do for you. With 30 users, it's hard enough to make things uniform. Having our own object library meant having everything LOOK consistant.&lt;BR /&gt;
&lt;BR /&gt;
Dividing options into objects. Having different objects for single doors, double doors, and bi-swing doors, especially before you could transfer parameters inside the Object Settings menu. Even cabinets had different 1-door, 2-door and 3-door objects. The DDGI Smart Parts approach was much more efficient and easier to understand, with separate doors by TYPE, such as "swinging" "bi-fold" and "sliding." Each type then allowed for various types within. Users found it much easier to understand, and it required only a handful of objects instead of a dozen or more.&lt;BR /&gt;
&lt;BR /&gt;
Sheer power. I saw the MSA detail library, and was rather underwhelmed, It was nice that GS included studs and bricks and fasteners, but even AutoCAD can do that. What impressed me was the batt insulation object. A very simple object with only a few parameters, but that repeated as needed to fill the void. Kind of the same thing that bricks and CMUs should do in section (or plan) details, like trusses should do in section (preferably 3D, but 2D will be fine), like a viny siding should do along the surface of a wall.... a little GDL and a few FOR/NEXT loops, and I have exactly that. It immediately simplified drawing wall/building sections with objects that can stretch to a certain length, and repeat within that length based on just a few parameters.&lt;BR /&gt;
&lt;BR /&gt;
Zero size errors. To me, if an object freaks out with a parameter set to "zero" or "none", or even a very small number like 1/16", that needs to be covered in the object's error checking (probably in the parameter or master script). "Invalid matrix generation" and other errors should not exist. Ever. No matter what parameter values the user enters. You want a 15'-0" x 0'-1" door? The object needs to either warn you when you type in the value, or it needs to accept the value without error. Finding out when you generate an elevation or when you get an unexplained error from Plotmaker/BGArchicad is too late.&lt;BR /&gt;
&lt;BR /&gt;
Organizaton. Stairmaker handrails and Doric columns are found under Division 3: concrete. Does this seem normal to anyone? Those railings do not look like concrete to me.....&lt;BR /&gt;
&lt;BR /&gt;
Construction methods. Most engineers place steel by the top of beam, not the bottom as the GS library does. That's a pretty major pain, since beams tend to not be normal dimensions. They are not 8", they are 8 3/64". It is kind of important that if an engineer tells you top of steel is 11'-3 3/4" that you are not trying to subtract off the size of the beam, especially if that beam size changes, with 4 different beam sizes changed to 4 other different beam sizes, then you have to both change the beam size AND change each beam's elevation by a different amount. Seems like a beam object placed to Top was pretty important.&lt;BR /&gt;
&lt;BR /&gt;
Railings. Since the Stairmaker railings border on useless, the only alternative was to use the railing objects. The railiings are placed by a total length (good) and a number of ballusters (????). They need to be placed by spacing of ballusters. Code requires a 4" sphere not fit between. That should be how the parameters can be entered. A center-to-center spacing is more important than the number, and the back-and-forth is pretty counterproductive, since even stretching a railing 3 or 4" can make a difference. "is 12 enough? how about 15? 16? 18? nope, too many, 17 it is!"  With manufacturers using architect's drawings for shops at an ever-growing rate in an ever-more-litigious world, its pretty important that this is correct. &lt;BR /&gt;
&lt;BR /&gt;
Slopes. Most parameters ask for angled objects like trusses and roofs in angles. Most Architects I know measure things in slope: how many inches per foot, or proportionally, how many feet per 12?&lt;BR /&gt;
&lt;BR /&gt;
Elevators. Sometimes elevators, like doors or windows, happen in pairs or trios or more, and some buildings have more than 12 floors. Kind of seems like an artificial limitaton&lt;BR /&gt;
&lt;BR /&gt;
Zones. Sometimes rooms have long names and need to be broken into multiple lines. Sometimes you want to move the tag at a certain scale and/or abbreviate the name and/or show the name or number only.&lt;BR /&gt;
&lt;BR /&gt;
Bathroom fixtures. Vanity cabinets can be bought down to 15", and sometimes we use them that small. The sink in the GS object protrudes from the cabinet at that size. Shouldn't the cabinet at least warn you about that? Or not accept the value? Or allow you to shrink the sink?&lt;BR /&gt;
&lt;BR /&gt;
Stairmaker (It's object-driven, so I'll vent here about that too). Where do I start.....  You cannot do concrete stairs at all (no rounded nosings), you really cannot do metal pan stairs (the sections are not quite right), the hand rails do not extend properly when you extend them the proper distance, the handrails do not show in plan, the arrows and text look terrible in plan, some stairs will not generate, even though their parameters are entered EXACTLY the way you want them built, and Archicad provides no guidance as to what the problem is..... I confess, I don't have my own stair objects..... yet.......&lt;BR /&gt;
&lt;BR /&gt;
Lighting and mechanical symbols. Not only is the GS selection weak, they also do not offer any internal display options to make them look decent, like separate pen and line colors, movable text, or even text at all sometimes. Sorry, a bunch of lines drawn to look like an "S" is a little sub-par in my book of Graphic Standards in the day of true-type and open-type fonts.&lt;BR /&gt;
&lt;BR /&gt;
Plumbing/gas riser symbols. Anyone heard of them? There were not any included in the GS library at all.&lt;BR /&gt;
&lt;BR /&gt;
Section markers. Again, way too many parameters for an object that should look the same every time (back to my "Defaults" complaint). Never mind the lack of an interior elevation-looking section marker. I long ago created a section marker that just looks the way it should, and has maybe 5 parameters: Overriding text values, a scale factor to cram it in small areas, and whether to include the side "wings" or not for sections versus elevations.&lt;BR /&gt;
&lt;BR /&gt;
Labels. Has anyone ever noticed that there is an option to "use symbol arrow" but none of the symbols actually have built-in arrows? Shouldn't that prompt read "use Archicad arrow?" I've long wondered that, and just recently started experimenting with stretchable hotspots inside a wall label, which pierces the wall by default, maybe even has a few extra arms to call out similar surrounding walls.... looks promising after a few hours of experimentation with the Label tool and its GDL values. &lt;BR /&gt;
&lt;BR /&gt;
Roof labels. How is it that in the days of BIM, no one realized that you can place labels on a roof and have it call out the roof's slope/elevation/pitch? I even went so far as to make a single object, which is context sensitive to show an arrow with "4:12" in plan and a right triangle that says "12" on the horizontal edge and a "4" on the vertical edge.... and, you guessed it, the edges of the triangle are proportional to the pitch of the roof.&lt;BR /&gt;
&lt;BR /&gt;
Cabinet labels. Why not make a label for kitchen cabinets that calls them out as "W1530" and make it look like a dimension and default above the cabinet for wall cabinets and below them for base cabinets?&lt;BR /&gt;
&lt;BR /&gt;
Trimwork. DDGI's "EasyTrim" object is among the most briliiant things I ever saw (once I removed that "enter-profile size" restriction). Enter a trim profile, place it all over, make it slope, make it twist, and make it so you can change the profile!! How is is that a 10K GDL object dating back to AC 6.5 or so from a 3rd part developer has more power than a full add-on from Graphisoft? &lt;BR /&gt;
&lt;BR /&gt;
OK, so I ran a little long here, and probably just boosted my word count beyond Karl, Matthew, and Djordje, but I think it was also a complete list of complaints I had with the Archicad library.... anyone want my reasons for creating our own Add-on? &lt;E&gt;&lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/E&gt;</description>
    <pubDate>Thu, 18 Aug 2005 19:42:03 GMT</pubDate>
    <dc:creator>TomWaltz</dc:creator>
    <dc:date>2005-08-18T19:42:03Z</dc:date>
    <item>
      <title>Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33514#M36601</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;WARNING:  THIS IS A  RANT ABOUT GS AND OTHER VENDORS OF POORLY WRITTEN AND INCONSISTENT LIBRARY PARTS.  So you may not want to waste your time reading this if you don't experience problems with library parts, in particular doors and windows.&lt;BR /&gt;
 &lt;BR /&gt;
Doors and windows are without question the most commonly used library parts in most ArchiCAD architectural projects.  Being continually frustrated by the limitations of so many of the libraries available to us ( not that there are many ).  So, recently I decided to try the new GS AC limited edition library for the US on a model with quite a few doors and windows. Initially I was excited to see what on the surface looked like a good set of doors and windows, with good adjustablility, especially for those who need fairly realistic looking windows and doors for their models. &lt;BR /&gt;
 &lt;BR /&gt;
That said, I have asked GS before, but they seem not understand the importance of being able to assign a different material selection for all exterior surfaces ( read, sash, frames, jambs, sills, aprons, trim, and the like) versus interior surfaces on doors and windows.  This may not be important if you don't use your models for renderings, but for those of us who do, it is a problem. It takes countless hours and attention to detail when sellecting parameters for materials so that your renderings will appear correctly both from the inside and out.  &lt;BR /&gt;
&lt;BR /&gt;
However, because of GS inflexible decision to continue to make window and door parts the way that they do,  models can not be made to look correctly, concurrently, both on the inside and outside where windows and doors have different material selections.  For buildings using, say aluminum storefront, not a problem, but for too many other building, it is.   This is absolutely maddening.  &lt;BR /&gt;
&lt;BR /&gt;
Oh, and while your at it GS it makes much more sense, even for those who don't assign materials to their objects, to gang all material selections under one heading called, oh I don't know, say MATERIALS!!!!!!!!!!!!&lt;BR /&gt;
 &lt;BR /&gt;
To help make matters worse, I just noticed that there is still an inconsistantcy in the GS windows in setting materials for different surfaces depending what wood windows you select.  On awing windows for instance the exterior trim color controls the interior trim color.  Yet on "W Single Hung2" window the interior and exterior trim colors are set independtly as they should be.  To make matters worse yet, the exterior sash color can not be set independent of the interior sash material, again rarely on a wood or aluminum clad window would this happen in the real world. &lt;BR /&gt;
&lt;BR /&gt;
It is really getting quite old to find window and door part developers not checking their parts thoroughly.  I don't want to single out GS on this either, as there is another major vendor here in the US of a large library that has doors and windows included in it that alledgely works well with AC 9.  This well known unamed library developer has SO MANY errors and inconsistantcies in its door and window library, its a joke.  I wrote that developer several times starting in February this year, and most of the errors I pointed out to him have not been fixed yet.  Yet that library is still available for sale at Objects Online as well as numerous locations on the web.  That particular developer has in the past always fixed found problems, but for what ever reason now just keeps selling "broken" library parts.....unbelievable!!!!!!&lt;BR /&gt;
 &lt;BR /&gt;
Unfortunately, people keep buying these libraries, and until a lot of time is invested in them, they might not find what inconsistantcies exist until it is crucial to them, usually the day before a presentation is due, and there is no time to fix the problem. &lt;BR /&gt;
 &lt;BR /&gt;
But Graphisoft really has no excuse for inconsistencies in their windows and doors.  Each of there parts should be fully tested, in straight and curved walls, and masonry veneer walls ( READ, EACH WINDOW AND DOOR FULLY TESTED ).  If GS doesnot  feel qualified to test their own parts, then they should hire some of their customer to independently to do so.   Im tired of haveing my office be a perpetual beta test site for library part developers!!!!!!!  I could NEVER get away with this sloppiness in my Architecture practice.  I'd be in court constantly. I spend way too much time taking screen shots, sending them to GS and other developers, only to find the problems ignored.   &lt;BR /&gt;
 &lt;BR /&gt;
If we go through the trouble of documenting the problems for you GS, you should take the responsibility to fix these problems, even its for just one user, if infact it is a real problem with the library part. &lt;BR /&gt;
 &lt;BR /&gt;
I am currently submitting over a dozen screen shots of inconsistencies to GS tech support us, for bad library parts.  Hopefully they will quickly resolve these issues and reissue the parts before v10 comes out.  But I'm guessing that GS is putting almost all of its efforts into v10 and problems found in AC 9.0 at this point, are being tabled indefinitely.&lt;BR /&gt;
&lt;BR /&gt;
Come on GS, we are on version 9.0!!!!!!!  Considering the current catch phrase is BIM, you would think you guys would get rid of all your dated, and unrealistic library parts, and finally commision top dog GDL developers to build really solid libraries, and contract them to keep them up to date.  Split 1 million dollars amongst ten GDL Gurus.....trust me they will come out of the wood work to jump on this opportunity. &lt;BR /&gt;
&lt;BR /&gt;
Your modeling capabilities are constantly limiting design, especially without the use of dozens of add-ons, and your library parts are dismal at best.  Look how few available parts there are available compared to the AutoCAD world.  Manufacturers throw themsleves at Autodesk customers with free parts.  And as BIM moves more from a marketing term to a real necessity, you guys keep churning out the same old tired parts....more and more Architects currently using AC will have no choice but to switch to Revit.  &lt;BR /&gt;
&lt;BR /&gt;
Radically improve your modeling and documentation tools.  Those who write to this forum are a minority of users, and while too many here seem willing to evangilize AC to their death at  any cost to the rest of us., most just want to get their job done faster and with more effeciency and industry standardization.  &lt;BR /&gt;
&lt;BR /&gt;
AutoCAD is going to hand you your lunch with a serving of REVIT if you guys don't stop repeating the same errors.  Listen and fix problems that users keep bringing to your attention, without being called out on the table, like......... ( disclaimer to readers, this is one of my wishlist items, this is really for GS benefit, just in case someones actually listening )&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?t=6583" target="_blank"&gt;&lt;LINK_TEXT text="http://archicad-talk.graphisoft.com/vie ... php?t=6583"&gt;http://archicad-talk.graphisoft.com/viewtopic.php?t=6583&lt;/LINK_TEXT&gt;&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
....hope this was more than entertaining to those who made it this far&lt;BR /&gt;
!&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 24 May 2023 10:48:19 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33514#M36601</guid>
      <dc:creator>rm</dc:creator>
      <dc:date>2023-05-24T10:48:19Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33515#M36602</link>
      <description>Rm,&lt;BR /&gt;
 you have to be really off your tits writing such a long story but I have to agree with you. The door and window elements are THE FUNDAMENTAL parts of any architecture and GS should pay really better attention to it. What about a proper library part, sort of prototypical and thorough example of a window/door that could serve as a standard for any 3rd party developer or basically anyone who wants to fiddle with openings. &lt;BR /&gt;
Talking about GDL development, it has started quite well during version 9 beta testing, when GS introduced a set of routines in GDL which are supposed to help a potential programmer with wall geometry etc. A fantastic idea but it hasn’t got any further.&lt;BR /&gt;
In conclusion – we are missing basic (and functional in real designing) parts in our libraries as oppose to having a 3D fire-extinguisher or even better an air diffuse in there.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;This well known unamed library developer has SO MANY errors and inconsistantcies in its door and window library, its a joke.&lt;/BLOCKQUOTE&gt;

Unfortunately, this is only ‘potent’ solution on the market at the moment capable creating windows/doors at least to some decent extent. But again, it’s a 3rd party developer working at level of GDL programming. GS, it’s a bit risky business…</description>
      <pubDate>Tue, 16 Aug 2005 05:26:07 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33515#M36602</guid>
      <dc:creator>Rob</dc:creator>
      <dc:date>2005-08-16T05:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33516#M36603</link>
      <description>&lt;BLOCKQUOTE&gt;Rob wrote:&lt;BR /&gt;Rm,&lt;BR /&gt;
 you have to be really off your tits writing such a long story but I have to agree with you. &lt;/BLOCKQUOTE&gt;

Rob,&lt;BR /&gt;
I'm not quite sure what your saying about my post, but I like the sound of it, and Im laughing my arse off.........I've got to get to Australia one day!&lt;BR /&gt;
&lt;BR /&gt;
But I'm glad you had the spirit to read the whole thing.  Now make me real happy and tell me you REALLY work for GS &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_lol.gif" style="display : inline;" /&gt;</description>
      <pubDate>Tue, 16 Aug 2005 05:36:16 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33516#M36603</guid>
      <dc:creator>rm</dc:creator>
      <dc:date>2005-08-16T05:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33517#M36604</link>
      <description>A useful link...&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://www.peevish.co.uk/slang/index.htm" target="_blank"&gt;http://www.peevish.co.uk/slang/index.htm&lt;/A&gt;</description>
      <pubDate>Tue, 16 Aug 2005 05:59:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33517#M36604</guid>
      <dc:creator>Rob</dc:creator>
      <dc:date>2005-08-16T05:59:00Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33518#M36605</link>
      <description>Yes, and I have almost forgotten. I don't work for GS...but considering my occasional frustration with AC/PM I feel sometimes like I should...</description>
      <pubDate>Tue, 16 Aug 2005 06:13:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33518#M36605</guid>
      <dc:creator>Rob</dc:creator>
      <dc:date>2005-08-16T06:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33519#M36606</link>
      <description>well said. all of it.&lt;BR /&gt;
&lt;BR /&gt;
nothing to add.</description>
      <pubDate>Tue, 16 Aug 2005 07:00:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33519#M36606</guid>
      <dc:creator>__archiben</dc:creator>
      <dc:date>2005-08-16T07:00:13Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33520#M36607</link>
      <description>Two things to add:
&lt;UL&gt;&lt;LI&gt;1) The AC library was limited enough that our company quickly came to the conclusion that instead if relying on GS and Objects Online, we would make our own.  On the plus side, I got good enough at it to do a little programming sidework and win a T-shirt for tip of the month &lt;E&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/E&gt;&lt;BR /&gt;
2) If you think they are inconsistant to use, you should try looking at the actual code. You can tell some of it is pretty old, and uses lovely variable names like "oc" or "m" (making it very difficult to figure out what's going on), not to mentions comments in German and Hungarian....&lt;/LI&gt;&lt;/UL&gt;Don't even get me started on what the doors &amp;amp; windows look like in section or at larger scales... &lt;BR /&gt;
&lt;BR /&gt;
It's a shame, since GDL is really an amazing technology. I've come to the conclusion that the AC library really is a great example of what COULD be done with Archicad, but is not so great for actual production. I would say that my office uses about 60% in-house objects, 35% ObjectOnline objects (many customized after purchase), and 5% GS objects.</description>
      <pubDate>Tue, 16 Aug 2005 13:29:56 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33520#M36607</guid>
      <dc:creator>TomWaltz</dc:creator>
      <dc:date>2005-08-16T13:29:56Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33521#M36608</link>
      <description>&lt;BLOCKQUOTE&gt;TomWaltz wrote:&lt;BR /&gt;The AC library was limited enough that our company quickly came to the conclusion that instead if relying on GS and Objects Online, we would make our own. &lt;/BLOCKQUOTE&gt;

We got the old (1998) SmartParts library after about ten minutes of using the AC (5.1) library. If you think it's bad now... &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_eek.gif" style="display : inline;" /&gt; I started doing GDL a year after that. A year later, we were using only my own windows and doors. I'm on about my fourth version of them now.&lt;BR /&gt;
&lt;BR /&gt;
The only parts we use from the AC library are things like furniture, appliances, faucets. We view these items as symbolic, and they don't have to be perfect, which, hoo-boy, they aren't. (Personal peeve: sinks can't operate in SEOs, so they can't cut the counter slab.) We won't invest time in making a perfect sofa object. (For other users, sofas might be critical.)&lt;BR /&gt;
&lt;BR /&gt;
(Near-)Perfect windows, doors, structure elements, symbols, and annotations &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;are&lt;E&gt;&lt;/E&gt; required, and we have invested a lot of time in creating/maintaining them. Pretty much every object in our projects that isn't furniture/fixture is home-grown.&lt;BR /&gt;
&lt;BR /&gt;
Yes, the libraries are bad, although they've been worse. Things like the interior/exterior sash material make me wonder if they've ever talked to a single american user, though I know they have. Truly bafflingly bad, and so easy to fix. My personal GDL hobby-horse is scale sensitivity, and the AC library makes very poor use of it. But they could fix all the big problems, and the libraries still couldn't meet the needs of thousands of users. User customization will always be needed.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;It's a shame, since GDL is really an amazing technology.&lt;/BLOCKQUOTE&gt;

I am permanently amazed that GS is actually sort of middle-of-the-pack in appreciating GDL's power. The power of objects isn't geometry (you can get geometry anywhere), it's parametrics. GDL is really the only tech for building custom parametric models from scratch.&lt;BR /&gt;
&lt;BR /&gt;
The investment I describe above, or Kitchen &amp;amp; Associates' investment, is not feasible for smaller, lower-margin, or solo-practice type firms. GDL isn't exactly hard, but starting it is a little hard, and it uses different skills from architectural, or drafting, practice. Yet customized libraries are critical to using AC to its potential IMO. Even if the AC libraries were great, they can't possibly meet everyone's custom needs. Look at all the parts. Look at all the &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;kinds&lt;E&gt;&lt;/E&gt; of parts. On top of developing AC itself, the AC library is hugely complex.&lt;BR /&gt;
&lt;BR /&gt;
What is needed is a graphical method for creating parametric objects. It needs to be easier for architects to make building elements that respond to the environment. If you want more people to make their own objects, and stop griping about the shipping libraries, the price of creating our own has to come down.&lt;BR /&gt;
&lt;BR /&gt;
Objects are critical to the success of the AC platform. GS has a choice: offer perfect libraries, or lower the bar for everyone doing it for themselves. The first isn't realistic, so here we are.&lt;BR /&gt;
&lt;BR /&gt;
With the development investment needed to make half the user base happy with the libraries, they could instead develop an environment to radically simplify the whole process, and let more people do more of it by themselves (and working together).&lt;BR /&gt;
&lt;BR /&gt;
The other thing that never seems to take off is manufacturers' creating their own stuff. Why on earth am I scripting a Marvin window? Why should Graphisoft? Again, if it were cheaper (easier) there would be more of it. Manufacturers also demand intellectual property protection. Whether they demand it reasonably is another matter, but GS should provide this facility for people who want it. Inability to control copying is a deal-breaker in the current IP climate.&lt;BR /&gt;
&lt;BR /&gt;
Update the tools, and work with the manufacturers, and the end-user library problems will quickly become tolerable.</description>
      <pubDate>Tue, 16 Aug 2005 15:05:10 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33521#M36608</guid>
      <dc:creator>James Murray</dc:creator>
      <dc:date>2005-08-16T15:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33522#M36609</link>
      <description>My view is also that GS should produce a solid set of generic doors and windows. &lt;BR /&gt;
&lt;BR /&gt;
I've ended up scripting all my own doors, windows, cabinets &amp;amp; plumbing fixtures. One of the primary reasons is that I want the power that GDL provides - Library parts that are scale variable (pen weights &amp;amp; level of detail); Library parts that know when they're rendered in plan, section or 3D views; and, a consistent user interface across each type of library part. Most of the current library symbols are too crudely implemented.&lt;BR /&gt;
&lt;BR /&gt;
I use about 1% of the GS library parts - and only if I'm desperate. I've tried tweaking them, but as previously mentioned, the antiquated and idiosyncratic coding make it almost impossible. &lt;BR /&gt;
&lt;BR /&gt;
Which is a shame, because GDL is one of the key features GS promotes. And it is a very powerful feature - but a few very well considered generic parts would be a real boon to helping GDL along.&lt;BR /&gt;
&lt;BR /&gt;
Cheers,</description>
      <pubDate>Tue, 16 Aug 2005 19:45:54 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33522#M36609</guid>
      <dc:creator>Vitruvius</dc:creator>
      <dc:date>2005-08-16T19:45:54Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33523#M36610</link>
      <description>So manufacturers interested in GDL cannot look at Graphisoft objects to see GDL at it's finest??</description>
      <pubDate>Tue, 16 Aug 2005 19:50:18 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33523#M36610</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2005-08-16T19:50:18Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33524#M36611</link>
      <description>&lt;BLOCKQUOTE&gt;Rashid wrote:&lt;BR /&gt;So manufacturers interested in GDL cannot look at Graphisoft objects to see GDL at it's finest??&lt;/BLOCKQUOTE&gt;

Pretty much, yeah. &lt;BR /&gt;
&lt;BR /&gt;
Though I do have to say, the TrusJoist guys did really well!</description>
      <pubDate>Tue, 16 Aug 2005 21:17:49 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33524#M36611</guid>
      <dc:creator>TomWaltz</dc:creator>
      <dc:date>2005-08-16T21:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33525#M36612</link>
      <description>I agree with all you guys. GS libraries are just not good enough. I use my own GDL object most of the time.</description>
      <pubDate>Wed, 17 Aug 2005 01:12:31 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33525#M36612</guid>
      <dc:creator>LiHigh</dc:creator>
      <dc:date>2005-08-17T01:12:31Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33526#M36613</link>
      <description>Back to the original topic. Could we finally get a library part of a window, door, niche/empty opening as standards. Properly analysed to details, like principals of opening, mullion, sill/threshold etc shaping, door/widow furniture and door panels/window panes libraries in easily extendable macros with proper description of parameters so any customised solution could be added by a local office GDL guru. So, for example, we would have a macro for ALL door panels in one with predefined parameters, a macro for handles and same with all other bits and pieces. I have to say we have some sort of organisation in it at the moment but yet again it’s not good enough. An example: we have 50 different door panels for internal doors why don’t we have them for bifolds???!!! Such silly (I would call them) mistakes really drive me schizo.&lt;BR /&gt;
&lt;BR /&gt;
It shouldn’t be so hard to analyse that just by looking at the door/window builder and considering that it was quite recently pretty much one-man-operation company.</description>
      <pubDate>Wed, 17 Aug 2005 02:42:34 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33526#M36613</guid>
      <dc:creator>Rob</dc:creator>
      <dc:date>2005-08-17T02:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33527#M36614</link>
      <description>&lt;BLOCKQUOTE&gt;Rob wrote:&lt;BR /&gt;Back to the original topic. Could we finally get a library part of a window, door, niche/empty opening as standards. Properly analysed to details, like principals of opening, mullion, sill/threshold etc shaping, door/widow furniture and door panels/window panes libraries in easily extendable macros with proper description of parameters so any customised solution could be added by a local office GDL guru. &lt;/BLOCKQUOTE&gt;

Hi Rob,&lt;BR /&gt;
&lt;BR /&gt;
Actually, the original topic WAS, that there are too many inconsistencies in door / window objects being put out on the market for sale both by GS and here in the US by GDL developers.  This IS the problem.  While I fully admire any office that can afford the resources to build there own GDL libraries, that strategy does nothing for the majority of offices, ( nor does it do ANYTHING for GS in sales ) that don't know how or have the time / budget to learn how to make GDL objects.  THIS strategy does NOTHING to further GS ability to convience large number of AutoCAD / Revit users to switch to ArchiCAD, and we ALL need them to do so.&lt;BR /&gt;
&lt;BR /&gt;
Imagine you have an office of say, ten architects........maybe you do, I don't mean to offend.  Now you use Revit, the AC salesperson gives you a good deal on AC.  Now he/she explains to you that you can not use paramentrically the 100,000 + objects available in the market allready to you in the AutoCAD world.&lt;BR /&gt;
&lt;BR /&gt;
Where do you think that sale is going...........NO-WHERE!&lt;BR /&gt;
&lt;BR /&gt;
GS talks about BIM this and BIM that.  They NEVER say in order to make AC fully capable, you REALLY need to learn GDL because we just don't have a very large database of libraries available to you, at least not ones that consistantly work well. &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_redface.gif" style="display : inline;" /&gt;  &lt;BR /&gt;
&lt;BR /&gt;
In a market like Chicago, which is a HUGE architecture market, do you know how hard it is to find Architects with AC experience, MUCH LESS GDL experience.  Lets be realistic here, MOST not all, but MOST people who worked to get an Architecture degree and work in the business want to be practicing architecture.  Writting GDL objects may be a creative process, but it is NOT practicing architecture......nor should any confuse it as doing so!  I personally dont care if I every "build" a GDL object again ( although I have done some simple ones ) I am way to busy running my office, designing buildings that work, that are functional and appealing to my clients and hopefullly my future clients. I have never had a prospective client ask, by the way, does your firm write its own scripts for GDL objects. GDL has no room in my radar, and if we switch to Revit sometime in the future, GDL will be bid a good-day!&lt;BR /&gt;
&lt;BR /&gt;
So, the original point is GS needs to get its act together ASAP on library parts ( but not JUST this ) and HIRE, YES HIRE, GDL "Experts"  to create new and reliable "FULLY TESTED" library parts, and start with the doors and windows!  Then they need to convince manufacturers to jump on board too, and make it as EASY as possible to get them involved.  Because without the manufacturing market jumping on board, you and I will all eventually be Revit users.  Maybe not today, or in a year, but within 5 years.&lt;BR /&gt;
&lt;BR /&gt;
That IS the point!</description>
      <pubDate>Wed, 17 Aug 2005 13:28:10 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33527#M36614</guid>
      <dc:creator>rm</dc:creator>
      <dc:date>2005-08-17T13:28:10Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33528#M36615</link>
      <description>&lt;BLOCKQUOTE&gt;rm wrote:&lt;BR /&gt;So, the original point is GS needs to get its act together ASAP on library parts ( but not JUST this ) and HIRE, YES HIRE, GDL "Experts"  to create new and reliable "FULLY TESTED" library parts, and start with the doors and windows!  Then they need to convince manufacturers to jump on board too, and make it as EASY as possible to get them involved.  Because without the manufacturing market jumping on board, you and I will all eventually be Revit users.  Maybe not today, or in a year, but within 5 years.&lt;BR /&gt;
&lt;BR /&gt;
That IS the point!&lt;/BLOCKQUOTE&gt;

  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_idea.gif" style="display : inline;" /&gt;  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_exclaim.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
Now I have nothing to add.</description>
      <pubDate>Wed, 17 Aug 2005 13:41:35 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33528#M36615</guid>
      <dc:creator>James Murray</dc:creator>
      <dc:date>2005-08-17T13:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33529#M36616</link>
      <description>I think I'll take this opportunity to also mention that the GDL/object interface is in serious need of an update. The graphical interfaces starting to appear in some objects are an improvement, but there are still a few other major items missing:
&lt;UL&gt;&lt;LI&gt;- Zoom in/out on previews. Nothing like changing a parameter on a 15'-0x12'-6" object and having no idea if anything changed&lt;BR /&gt;
- Full rotation of previews, without actually changing the object's rotation angle (like a mini 3D window)&lt;BR /&gt;
- More than one level of "expandable" headers&lt;BR /&gt;
- Better methods for 3D linetypes (dashed lines in 3D are currently arrays of small solid lines with gaps between them!)&lt;BR /&gt;
- Ability to select multiple parameters of the same type (like selecting all pens or fills)&lt;BR /&gt;
- Ability to set all objects to a company standard, such as all door swings to pen 19 or all fonts to Architext.&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Wed, 17 Aug 2005 14:31:26 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33529#M36616</guid>
      <dc:creator>TomWaltz</dc:creator>
      <dc:date>2005-08-17T14:31:26Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33530#M36617</link>
      <description>&lt;BLOCKQUOTE&gt;rm wrote:&lt;BR /&gt;...Writting GDL objects is may be a creative process, but it is NOT practicing architecture...&lt;/BLOCKQUOTE&gt;

Exactly rm,&lt;BR /&gt;
&lt;BR /&gt;
I personally like programming process, especially when I do that for my  projects, but I'm architect and working on drawings, doing sketches etc is more creative process for me than working on software omissions.&lt;BR /&gt;
&lt;BR /&gt;
I would like to use GDL only in very specific cases. Software developers must care only automating processes and write more universal programs.&lt;BR /&gt;
So back 2 original post that's means, that we need more universal and independent DWs, structural elements, etc.. We architects must care about design and not GS or Autodesk. They are "soft. developer companies" and must work in the way to develop CAD and not theoretical projects to be more original, the last is our job &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_smile.gif" style="display : inline;" /&gt;.&lt;BR /&gt;
&lt;BR /&gt;
So I fully agree all that's above. We need next generation universal libraries and also universal tools to develop these lib-s much more easier, without waiting new lib releases from GS. And finally i just want to spend time on GDL programing process for my creative profession &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_smile.gif" style="display : inline;" /&gt;.</description>
      <pubDate>Wed, 17 Aug 2005 15:25:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33530#M36617</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2005-08-17T15:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33531#M36618</link>
      <description>I fully agree with all this. &lt;BR /&gt;
&lt;BR /&gt;
May i add another point. To write his own parts is one thing. To maintain them through different versions of AC is another pain. &lt;BR /&gt;
When some old features suddenly work differently with a new release, this is very anoying.&lt;BR /&gt;
 &lt;BR /&gt;
I think to mask values for wallhole and cutpolya, completly changed from 7 to 8, without any warning or explanation.&lt;BR /&gt;
Detail, OK, but consequences are significant.</description>
      <pubDate>Wed, 17 Aug 2005 15:57:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33531#M36618</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2005-08-17T15:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33532#M36619</link>
      <description>I have nothing to add to the comments below either.   &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_eek.gif" style="display : inline;" /&gt;  (It is difficult even teaching GDL when "none" of the library objects is a good example of how things should be written and documented.)&lt;BR /&gt;
&lt;BR /&gt;
But, on a constructive note, perhaps the US people who have posted to this thread could comment on the revised doors/windows in the SE 9 library and give specific feedback to GS on what works, and what does not?&lt;BR /&gt;
&lt;BR /&gt;
I agree with all of the general gripes and emotion (!) ... but I think specific and constructive requests are more likely to receive attention.&lt;BR /&gt;
&lt;BR /&gt;
My 2 cents,&lt;BR /&gt;
Karl</description>
      <pubDate>Wed, 17 Aug 2005 16:58:42 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33532#M36619</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2005-08-17T16:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: Poorly written GDL Part Libraries</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33533#M36620</link>
      <description>&lt;BLOCKQUOTE&gt;Karl wrote:&lt;BR /&gt;But, on a constructive note, perhaps the US people who have posted to this thread could comment on the revised doors/windows in the SE 9 library and give specific feedback to GS on what works, and what does not?  &lt;BR /&gt;
  &lt;BR /&gt;
Karl&lt;/BLOCKQUOTE&gt;  &lt;BR /&gt;
  &lt;BR /&gt;
Karl,  &lt;BR /&gt;
  &lt;BR /&gt;
Since I'm in that group, I will respond.  I have sent files to tech support.  The objects are plagued with problems, and I had to compile numerous screen shots to indicate what the problems are that I found to this point. Needless to say, it is very time consuming assembling screen shots, writing little narratives, than packaging it so it is clear to the recipient.  I just didn't see the need to post those items here.  I also have done so with the SmartParts 9.0 Library.  But that has not done much good either.  &lt;BR /&gt;
  &lt;BR /&gt;
I think that my original posts are clearly in line with almost everyone who has posted here!  I know you try to help people as much as you can on this forum, but you jumped the gun a little on your suggestion here.  &lt;BR /&gt;
  &lt;BR /&gt;
I have numerous emails into GS for found library part inconsistencies.  In this case I decided to be go public with the need for improvement, because I'm tired of wasting time with tools that simply don't work as advertised.  Every 18 months +/- we get a new upgrade from GS.  It sometimes takes months for problems to crop up in design and production of construction documents while using AC.  By that point GS is already moving on to the next "upgrade" and we are left holding the bag......that's unacceptable anymore from GS, Abvent or MS as far as I'm concerned.  I invest too much money for half-backed software, and I'm sick of it.  If you paid retail for all your software, you might see my point here.   &lt;BR /&gt;
  &lt;BR /&gt;
Resellers and related consultants can make all the excuses they want for the shortcomings of the software they represent, or gain income from by espousing its virtues; but architecture and design firms need to keep their office efficient.  Just as in construction, sometimes a bigger hammer gets the job done faster.  I decided to use a 5lb. hammer, I could have used a sledge hammer instead. &lt;BR /&gt;
  &lt;BR /&gt;
But thanks for your suggestion, none the less.  I know it was meant to help &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_eek.gif" style="display : inline;" /&gt;</description>
      <pubDate>Wed, 17 Aug 2005 18:06:44 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Poorly-written-GDL-Part-Libraries/m-p/33533#M36620</guid>
      <dc:creator>rm</dc:creator>
      <dc:date>2005-08-17T18:06:44Z</dc:date>
    </item>
  </channel>
</rss>

