Can a GDL element produce multiple instances in interactive schedules?

[Sam Karli]

Hi,

I'm about to create an AC Goodies Wall addon that places (story-high) wall panels. The placeable macro of the addon is for a complete wall that consists of multiple panels (btw these are represented by, by default, non-placeable macros).

The question is whether it is possible to collect these panels so that I can display them, with their view, in an interactive scheduling, like doors and windows. Archicad should count them one by one and display one of them.

For doors, this looks like this:

But for walls, like this:

Note that walls are displayed having 4 panels in each.

The alternative approach -that i want to avoid- to write a C++ plugin that places elements one by one and this way they may become schedulable.

PS note that one wall element consists of more than one type of panels (multiple sizes), so it's not enough to make a preview of a wall displaying one panel only.

AFAIK using components should be the solution with the exception that these cannot be displayed.

I think this is a commonplace in Archicad (at least I saw many similar, brick-placer wall addons).

Thanks in advance.

[Barry Kelly]

As the accessory will be one object per wall, I think you will find you will only be able to schedule that one entire object.

Not the individual parts of that object.

It is not a hierarchical object like stairs, rails or curtain walls where you can schedule the sub-parts.

Barry.

[Toper Barrientos]

Hi,

Built-in schedule/listing by Archicad cannot display one-dimensional parameter array, AFAIK.. Youre LOOPING your panels    in that wall accessory, as ive done myself.. Hence ,  i created a pseudo-list 

using Elevation view where i incorporated a 3d texts display of the  ID's, panel sizing,etc (e.g i want to create a cut list of those diff panels)   showing in elevation view only. 

Manual  workaround with scripts: publish your "wall panels" as Ifc.. hotlink   to a separate file as  exploded elements (morph) ,then, list those elements.

[Sam Karli]

Thanks for Your quick reply, that was that I was afraid of.

It's interesting that such a commonplace thing is not solved for around 40 years, in many cases this comes out.

[Sam Karli]

Thanks, this workaround seems so complicated that it's the easier way to write a plugin C++.