<?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: Add-on for rounding measurements in Archicad C++ API</title>
    <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359731#M1655</link>
    <description>&lt;P&gt;Hey! I developed such label to our architecture firm and it currently belongs to our own library. But I could develop a similar label suiting your needs. Being the case you may e-mail me&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; (&lt;A href="mailto:pedrocollares@gmail.com" target="_blank"&gt;pedrocollares@gmail.com&lt;/A&gt;)&lt;/P&gt;</description>
    <pubDate>Mon, 24 Oct 2022 22:25:42 GMT</pubDate>
    <dc:creator>pedrocollares</dc:creator>
    <dc:date>2022-10-24T22:25:42Z</dc:date>
    <item>
      <title>Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359599#M1644</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wonder if there's an add-on ever made for the following purpose:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In a current project we're developing, there's a bunch of bad measurement values (for example, 25.03 cm instead of 25.00 cm). And they're always really close to the correct measurement value.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Logically, we don't need the ".03" amount, it is only a matter of design inaccuracy. It would be great if we could run an 'element rounding-off' plug-in, which snaps every selected element to the closest round measure (admitting 0.5 and maybe 0.25), considering the project origin as a major reference to those measurements.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone ever heard of such?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 02:56:10 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359599#M1644</guid>
      <dc:creator>pedrocollares</dc:creator>
      <dc:date>2022-10-24T02:56:10Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359602#M1645</link>
      <description>&lt;P&gt;why not change the settings in the Project Preferences?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="GerryLeonor_0-1666580722384.png" style="width: 400px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/30875i1917B9284D7AC7FB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="GerryLeonor_0-1666580722384.png" alt="GerryLeonor_0-1666580722384.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Working Units&lt;/STRONG&gt; is what will be displayed in your dimension tracker, door / window sizes, wall heights etc. if you set it to Meter, your door leaf will be 0.9 x 2.04m in size. if you set it to Millimeter, it'll be 900 x 2040mm in size.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the &lt;STRONG&gt;Dimensions&lt;/STRONG&gt;&amp;nbsp;settings will be the output of your dimensions &amp;amp; will print / publish depending on what you've set it to. there are already some out of the box Dimension Combo in there. see what fits best, otherwise make it suit your own.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 03:11:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359602#M1645</guid>
      <dc:creator>Gerry Leonor</dc:creator>
      <dc:date>2022-10-24T03:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359603#M1646</link>
      <description>&lt;P&gt;Those configurations will only allow me to hold accuracy in my documentation, and that could be enough, but when we collaborate with other appointed parts in projects&amp;nbsp;(Which might even work in different units/dimension settings) we need to maintain our model accuracy, more than only documentation.&lt;BR /&gt;&lt;BR /&gt;Small flaws in measurements can put out errors in collaboration, such as beam/wall bad overlapping and so on. We have guidelines of never modeling in measures not divisible by 0.25cm, and such tool I mention above would make auditing easier.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 03:40:27 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359603#M1646</guid>
      <dc:creator>pedrocollares</dc:creator>
      <dc:date>2022-10-24T03:40:27Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359605#M1647</link>
      <description>&lt;P&gt;yes, i understand. you want to control the accuracy down to the modelling level &amp;amp; not up at the documentation level.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;this has always been an issue for the juniors in our office. in our last internal CAD lunch talk, i had to go through &amp;amp; show them how to model things orthogonally to avoid having walls at an 89.9994 angle &amp;amp; have odd dimensions like 1203.04mm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;unfortunately i can't think of a way to avoid tiny dimension mishaps such as these without having to do 2 or 3 extra steps beyond the typical modelling methodology. (eg. modelling walls orthogonally to the side to avoid grabbing a random spot in the active model &amp;amp; using that as a snap guide reference which could cause mis-alignments a few steps ahead.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;perhaps turning on the Grid Snap feature will alleviate some of it? i couldn't stand it for more than 5 minutes. i'm open to hear of other solutions for this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;to me, this part of the software was either too smart by allowing these miniscule dimensions, or too dumb to actively prevent such tiny misalignments.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 04:03:34 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359605#M1647</guid>
      <dc:creator>Gerry Leonor</dc:creator>
      <dc:date>2022-10-24T04:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359608#M1648</link>
      <description>&lt;P&gt;We have a few ways of trying to avoid it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The grid is one, but it is too rigid in such a way you'll always turn it off eventually.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We even crafted a custom label in GDL meant for auditing, to figure out if elements X and Y coordinates to the project origin are divisible by 0.25, and if their rotations are OK.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pedrocollares_0-1666584530472.png" style="width: 400px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/30876iF7AD7F91A5850596/image-size/medium?v=v2&amp;amp;px=400" role="button" title="pedrocollares_0-1666584530472.png" alt="pedrocollares_0-1666584530472.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But once inaccuracy is there (Projects go through many different hands), having to deal with it can be frustrating.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since I'd be able to instruct exactly what I'd want that imaginary add-on to do, it seems to me a feasible thing. I might dive into crafting add-ons at some point just to put up that thing&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":grinning_face_with_sweat:"&gt;😅&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 04:18:40 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359608#M1648</guid>
      <dc:creator>pedrocollares</dc:creator>
      <dc:date>2022-10-24T04:18:40Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359612#M1649</link>
      <description>&lt;P&gt;yes, we've started to implement model checking tags such as that in our template, thought not as clean as yours. it's a shame it's gotten to that degree &amp;amp; still annoyed it's not dealt with at the earliest stage -- during the modelling of elements.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;apologies if my first answer sounded condescending. didn't read your signature &amp;amp; assumed it was a CAD junior asking for tips.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 04:32:06 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359612#M1649</guid>
      <dc:creator>Gerry Leonor</dc:creator>
      <dc:date>2022-10-24T04:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359636#M1650</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The cost of these errors increases as models becomes more advanced while at the same time the relative cost of avoiding these errors increases as it becomes easier to model freely.&amp;nbsp;I think this is a real problem that warrants a solution from GS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To me the obvious solution is to decrease the cost of avoiding these errors by implementing the ability to&amp;nbsp;&lt;A href="https://community.Graphisoft.com/t5/Wishes-forum/Lock-input-to-Working-Unit-s-number-of-decimals/m-p/335333/highlight/true#M19933" target="_self"&gt;lock input to working units number of decimals&lt;/A&gt;. Graphical input methods are likely to be the culprit behind most of these errors and if the input could be locked in terms of decimals a lot of errors would be avoided. This would also allow for much more efficient modelling throughout the design process as we&amp;nbsp;to a large extent could rely solely on graphical input.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 08:44:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359636#M1650</guid>
      <dc:creator>hevi</dc:creator>
      <dc:date>2022-10-24T08:44:21Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359673#M1651</link>
      <description>&lt;P&gt;Same problems here, very frustrating. We Also often waste a lot of time to restoring our files.&amp;nbsp;Lock Imput seams to be a great idea!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Graphisoft what do you think?&lt;/P&gt;&lt;P&gt;Fabio&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 14:16:24 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359673#M1651</guid>
      <dc:creator>fabioferrini</dc:creator>
      <dc:date>2022-10-24T14:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359674#M1652</link>
      <description>&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":cool_button:"&gt;🆒&lt;/span&gt;&amp;nbsp;Great solution! I will be impertinent, but could you please kindly share with us the GDL script of these great labels? Thanks in advance&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":folded_hands:"&gt;🙏&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Fabio&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 14:32:09 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359674#M1652</guid>
      <dc:creator>fabioferrini</dc:creator>
      <dc:date>2022-10-24T14:32:09Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359676#M1653</link>
      <description>&lt;P&gt;I run two different dimension systems that can be switched in the Quick Settings at the base of the screen. The standard one is WYSIWYG as published and assigned to the View settings. The other shows the smallest value possible, so any dimensions can quickly show the errors without the displayed extra accuracy impacting the View &amp;amp; Published layout.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Behind the scenes I think things are getting a bit messy with AC. I have always been super critical of my own drawings, but I am generating a growing number of errors. It is difficult to pin down but I think the following are part of the problem...&lt;/P&gt;&lt;P&gt;1. GS are reducing processing accuracy to increase display speeds of increasingly complex elements.&lt;/P&gt;&lt;P&gt;2. AC is prone to pick up on element nodes that are irrelevant to the current drawing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. The blue guide lines can throw unwanted intersections into the pot, particularly when the circular guides start to appear just off the required point.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 14:33:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359676#M1653</guid>
      <dc:creator>DGSketcher</dc:creator>
      <dc:date>2022-10-24T14:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359679#M1654</link>
      <description>&lt;P&gt;that would be great... if it existed it would win the award for the best useful plug-in in the world, for our studio!&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 14:40:39 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359679#M1654</guid>
      <dc:creator>fabioferrini</dc:creator>
      <dc:date>2022-10-24T14:40:39Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359731#M1655</link>
      <description>&lt;P&gt;Hey! I developed such label to our architecture firm and it currently belongs to our own library. But I could develop a similar label suiting your needs. Being the case you may e-mail me&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; (&lt;A href="mailto:pedrocollares@gmail.com" target="_blank"&gt;pedrocollares@gmail.com&lt;/A&gt;)&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 22:25:42 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359731#M1655</guid>
      <dc:creator>pedrocollares</dc:creator>
      <dc:date>2022-10-24T22:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359901#M1656</link>
      <description>&lt;P&gt;here's a quick&amp;nbsp; demo for an addon checking wall length:&lt;/P&gt;&lt;P&gt;It checks all selected walls&amp;nbsp; and change the cut fill to red if&amp;nbsp; its length is not a multiple of the 'step' variable. This gives a quick visual reference to find errors in the model.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="cpp"&gt;    void lengthCheck()
    {
        API_GetPointType     pointInfo;
        GS::Array&amp;lt;API_Guid&amp;gt;  inds;
        GSErrCode            err;
        API_SelectionInfo    selectionInfo;
        API_Elem_Head        tElemHead = {};
        GS::Array&amp;lt;API_Neig&amp;gt;  selNeigs;
        double  startX, endX, startY, endY, theta, dx, dy, Lprev,step,rem,L,eps;
        Int32               index;
        GS::UniString       strType,dir;
        GS::UniString       name, strName;
        API_Element         element = {} , mask;

        err = ACAPI_Selection_Get(&amp;amp;selectionInfo, &amp;amp;selNeigs, true);
        BMKillHandle((GSHandle*)&amp;amp;selectionInfo.marquee.coords);
        if (err != NoError &amp;amp;&amp;amp; err != APIERR_NOSEL) {
            ErrorBeep("ACAPI_Selection_GetInfo", err);
            return;
        }

        ACAPI_ELEMENT_MASK_CLEAR(mask);
        ACAPI_ELEMENT_MASK_SET(mask, API_WallType, penOverride.overrideCutFillBackgroundPen);
        ACAPI_ELEMENT_MASK_SET(mask, API_WallType, penOverride.cutFillBackgroundPen);
        ACAPI_ELEMENT_MASK_SET(mask, API_WallType, penOverride.cutFillPen);
            for (index = 0; index &amp;lt; selectionInfo.sel_nElemEdit; index++) {
                // Get selected element
                BNZeroMemory(&amp;amp;element, sizeof(element));

                element.header.guid = selNeigs[index].guid;
                if (ACAPI_Element_Get(&amp;amp;element) != NoError) 
                    continue;

                startX = element.wall.begC.x;
                startY = element.wall.begC.y;
                endX = element.wall.endC.x;
                endY = element.wall.endC.y;

                step = 0.002500;
                eps =  0.0000100;


                if (abs(endX) &amp;gt; abs(startX)) {
                    dx = abs(endX - startX);
                }
                else {
                    dx = abs(startX - endX);
                }

                if (abs(endY) &amp;gt; abs(startY)) {
                    dy = abs(endY - startY);
                }
                else {
                    dy = abs(startY - endY);
                }
                
                
                L = sqrt(dx * dx + dy * dy);

                theta = atan2(dx, dy) / (2 * PI) * 360;

                if (dx &amp;lt; eps &amp;amp;&amp;amp; dy &amp;gt; eps)  //vertical wall
                {   
                    Lprev = dy ;
                }

                if (dx &amp;gt; eps &amp;amp;&amp;amp; dy &amp;lt; eps)  //horizontal wall
                {
                    Lprev =  dx;
                }

                if (dx &amp;gt; eps &amp;amp;&amp;amp; dy &amp;gt; eps)       //if not orthogonal wall
                {
                    Lprev = L ;
                }
                rem = fmod(Lprev, step);
       
                if (rem &amp;gt;= eps &amp;amp;&amp;amp; rem &amp;lt;  step - eps) {
            
                    element.wall.penOverride.overrideCutFillBackgroundPen = true;
                    element.wall.penOverride.cutFillBackgroundPen = 181;
                    element.wall.penOverride.cutFillPen = 181;

                    ACAPI_CallUndoableCommand("Element Test API Function",
                        [&amp;amp;]() -&amp;gt; GSErrCode {

                            err = ACAPI_Element_Change(&amp;amp;element, &amp;amp;mask, nullptr, 0, true);
                            if (err != NoError) {
                                ErrorBeep("elem change err", err);
                            }
                            return err;
                        });  
                }
            }
            return ; 
    }&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Wed, 26 Oct 2022 05:41:55 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359901#M1656</guid>
      <dc:creator>julienK</dc:creator>
      <dc:date>2022-10-26T05:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359902#M1657</link>
      <description>&lt;P&gt;Dear juliencuadra,&lt;/P&gt;&lt;P&gt;thank you so much! &lt;span class="lia-unicode-emoji" title=":red_heart:"&gt;❤️&lt;/span&gt;&lt;/P&gt;&lt;P&gt;have a nice day&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fabio&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 05:43:48 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/359902#M1657</guid>
      <dc:creator>fabioferrini</dc:creator>
      <dc:date>2022-10-26T05:43:48Z</dc:date>
    </item>
    <item>
      <title>Re: Add-on for rounding measurements</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/361611#M1658</link>
      <description>&lt;P&gt;I'm developing that but still wasn't able to finish it.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Nov 2022 17:00:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Add-on-for-rounding-measurements/m-p/361611#M1658</guid>
      <dc:creator>vdentello</dc:creator>
      <dc:date>2022-11-09T17:00:30Z</dc:date>
    </item>
  </channel>
</rss>

