topic Re: project2{4} in GDL

project2{4}

Paalanen — Fri, 28 Jan 2022 13:07:28 GMT

Hello everybody!

project2{4} again, sorry: Seems I cannot avoid the projected filltype overriding the cut filltype. I.e. I can't control the two fills separately, as I can the pens:

methodx=3+32+512 partsi=1+2+4+8 project2{4} 4, 0, 0, 0, 0, methodx, partsi, 12, ! cut fill 1, 0, 0, 0, -SYMB_ROTANGLE, cutPen, SYMB_LINETYPE, ! cutLinePen, cutLineType 0, ! projected fill overrides cut fill !!! 0, 0, 0, 0, 0, projectPen, SYMB_LINETYPE, ! projectedLinePen, projectedLineType

Any comments appreciated!

Re: project2{4}

Peter Baksa — Wed, 26 Jan 2022 08:24:05 GMT

Hi Paalanen,

This is how it works, from AC20 project2{4} and project2{3} the attributes of the cut polygons are defined by the cover fill of the outer surfaces (in case the addition modifier 32 is not set).

There is a rather complicated workaround:
– each piece of the model that has the same building material can be projected using project2{3} ... parameters to model only that part, fills overridden with the attributes from a “Building_Material_info” request.
– the visible and overhead parts have to be projected in a separate call, they show correctly only with a full model.
For an example see “CWFrameRegDouble” macro.

Re: project2{4}

Paalanen — Sat, 29 Jan 2022 17:44:19 GMT

Thank you very much. I'll take a look at the macro.

Re: project2{4}

Paalanen — Fri, 18 Feb 2022 09:39:00 GMT

Péter, is it so, that the (possible) parameters at the end of project2-commands cannot be arrays?

Re: project2{4}

Peter Baksa — Tue, 22 Feb 2022 14:54:50 GMT

If you mean the PARAMETERS passed to the library part, they can, if they are array parameters in the object.

Re: project2{4}

Paalanen — Sun, 27 Feb 2022 04:14:05 GMT

Thank you very much for your reply. Below's what I mean. The commented "basic" parameters work just fine. But a corresponding array-parameter-attempt gives the error "Missing parameter value". Any thoughts?

project2{4} 3, 0, 0, 0, 1, leikk[1], !-Cut height methodx, partsi, 1, !---Fill 2, 0, !---FillPen, FillBgPen 0, 0, -SYMB_ROTANGLE, 21, 1, !---cutLinePen, cutLineType 0, !---Fill 19, 0, !---FillPen, FillBgPen 0, 0, 0, 1, 1, !---projectedLinePen, projectedLineType 0, 0, 1, !---Fill 1, 1, !---FillPen, FillBgPen 0, 0, -SYMB_ROTANGLE, 1, 1, !---cutLinePen, cutLineType 1, !---Fill 1, 1, !---FillPen, FillBgPen 0, 0, 0, 1, 1, !---projectedLinePen, projectedLineType ! parameters test1 = 1, ! test2 = 0 parameters test[1] = 1, test[2] = 0

Re: project2{4}

Peter Baksa — Wed, 02 Mar 2022 08:43:33 GMT

Only whole arrays can be passed:

dim _test[] ! using underscrore to keep original test parameter's values in the rest of the script _test[1] = 1 _test[2] = 0 project2{4} ... parameters test = _test

Re: project2{4}

Paalanen — Wed, 02 Mar 2022 09:13:42 GMT

Ah, beautiful! Köszönöm szépen!

Re: project2{4}

Paalanen — Tue, 30 Aug 2022 12:40:52 GMT

Hello Péter,

Been working with the project2{4} command quite successfully until now. Holes using cutform punched into my projected prism are projected as cut shapes instead of projections. Tried and failed fiddling with the status and mask codes.

Attaching a screenshot of a prism projected from the front - The circles are "cutforms", the left one is an infinite cut (status 1+8+16) and the right semi-infinite (status 1+16). The correctly projected rectangular opening is defined in the prism itself.

Would be super greatful for some guidance once again.

Re: project2{4}

Peter Baksa — Mon, 05 Sep 2022 08:53:39 GMT

What is your code for this?

Re: project2{4}

Paalanen — Fri, 09 Sep 2022 20:12:44 GMT

Hello and thank you very much for your response!

Here's a simplified version:

3d:

!status = 1+8+16 status = 1+16 !-Not through status2 = 5 side = 2 : n = 15 add side/2, side/3, side/2 cutform{2} 4, 1, status, 0, 0, -1, .2, .1, 0, status2, 0, 0, 900 + status2, 0, 180, 4000 + status2, 0, 180, 4000 + status2 del 1 put 0, 0, 0, n, 1, 0, side, 0, n, 1, side, side, 0, n, 1, side, 0, 0, n, 1 cprism_{2} 1, 1, 1, nsp/5, side/2, get(nsp) cutend 2d: methodx=3+32+512 partsi=1+2+4+8 project2{4} 3, 0, 0, 0, 1, cutHeight, methodx, partsi, _fillType, ! Cut Fill _penFgFill, _penBgFill, ! Cut FillPen, Cut FillBgPen 0, 0, -SYMB_ROTANGLE, SYMB_SECT_PEN, SYMB_LINETYPE, ! Cut LinePen, Cut LineType 0, ! Fill 19, 0, ! FillPen, FillBgPen 0, 0, 0, SYMB_VIEW_PEN, 1, ! Projected LinePen, Projected LineType 0, 0, 1, !---Fill 1, 1, !---FillPen, FillBgPen 0, 0, -SYMB_ROTANGLE, 1, 1, !---cutLinePen, cutLineType 1, !---Fill 1, 1, !---FillPen, FillBgPen 0, 0, 0, 1, 1

Re: project2{4}

Paalanen — Fri, 09 Sep 2022 09:13:27 GMT

Re: project2{4}

Paalanen — Fri, 09 Sep 2022 12:08:34 GMT

Actually, another thing is bothering me, trying to find workarounds: The basic project2-command draws the cutform shapes with a solid line regardless of a line_type-command (,that otherwise works):

line_type test_line
project2 3,270,2+32

Re: project2{4}

Peter Baksa — Mon, 12 Sep 2022 10:13:39 GMT

Hi,

you need to set status j2 in CUTFORM (generated cut polygons will be treated as normal polygons), otherwise the circular surface of the cut will be a cut polygon, and PROJECT2 treats it as such, regardless its position in space.

With PROJECT2{3} cut surfaces can only be created by cutting the model with cut commands. PROJECT2{4} also cuts the model on its own, but inherits cut surfaces from different cut commands.

You can use SECT_ATTRS with PROJECT2{3} to change cut edges' line types.

Re: project2{4}

Paalanen — Tue, 20 Sep 2022 09:53:44 GMT

Thank you very much once again. Status j2 in CUTFORM got indeed rid of the cut surface (fill) from the circular shape. However, using PROJECT2{4} the outline of it remained cut (,dependent on Cut Line Pen setting in the object's CUT SURFACES settings). I.e. it does not seem to be possible to control neither the pen nor the line type of the cutform projection. Using PROJECT2 and PROJECT2{3} with SECT_ATTRS the problem is similar; one cannot control the line type of the cutform projection - it remains solid.

Am I missing something or could this be called a bug / characteristic?

Re: project2{4}

Peter Baksa — Wed, 05 Oct 2022 09:29:48 GMT

Yes, it can be called a bug.

If there are no other cut lines in your projection, you can use flag 32 in the method parameter to override the cut line attributes.

https://gdl.Graphisoft.com/tips-and-tricks/explore-the-project23-command

Re: project2{4}

Paalanen — Tue, 18 Oct 2022 10:07:14 GMT

Thanks again Peter. I guess I'll go looking for a workaround... I guess there's no way of knowing wether Graphisoft will fix this "bug" or not?

Kind regards!