Make a single Gdl object count as multiple objects

[Anonymous]

Hi guys.

I´ve been asked by a client ot modify an object, in order to make this single object count as 1, 2, 3 etc. objects in their schedule.

The object is a shelf, and I can easily write the gdl code for multiple shelfes distributed along the Z axis.

However the client wants each shelf to count as 1 in their schedule without having to place several similiar objects above each other....

I´m sorry if theres already a thread concerning his topic. This is my first post in this forum...

I just need to know if it is possible at all...

Thank you!

Kind regards M7

[Barry Kelly]

No the schedules can only count one object once.
However you could create a parameter in your object for the number of shelves (you will already have this if you can do multiple shelves).
You can then display this parameter in the schedule so you can see the number of shelves.
But this would not work if you use multiple objects as they would.
If you don't have the merge identical items checked then they will all list as separate shelves.
Then if you do have the merge checked you will only see the number of shelves per unit if they are the same (not a total) and will list as separate shelves if they have different number of shelves.

Far easier to add one shelf and multiply it in Archicad.
Then schedule the actual shelve placed.

Barry.

[Anonymous]

Hi Barry.

Thank you.

I know how to create a parameter for adding shelfes/geometry in the object, and this is the solution I will suggest to my client.

However, it was important to know if an object could count as multiple....
both out of curiosity, and for future gdl coding...

Once again, thank for that quick reply 😉

Regards M7 / Thomas

[Barry Kelly]

I have moved this topic to 'schedules' which is a better spot for it.

As you can see in the image the listing of the multiple shelf parameter really won't work as it doesn't add the parameter with the others of the same number.

Barry.

[Barry Kelly]

It is possible to use the 'Sum' and 'Flag' options to get a slightly better result - but I still don't think this is as clear as placing individual shelf objects and simply counting them each as one.

Barry.

[Anonymous]

Barry wrote:
It is possible to use the 'Sum' and 'Flag' options to get a slightly better result - but I still don't think this is as clear as placing individual shelf objects and simply counting them each as one.

Barry.

I think If you move the quantity on the second column it will look better and make sense.

How about calling the self as a macro into the object that does the spreading and then scheduling the macro?
Would that work?

[Barry Kelly]

ispyridis wrote:
How about calling the self as a macro into the object that does the spreading and then scheduling the macro?
Would that work?

Not that I am aware of.
You are not placing the macro and Archicad will count only what you place.
So it won't see the macro to count it.

Another option (although not that good) is to model your multiple shelves as one object.
Then off to the side (or in another storey if yo are not worried about schedule storeys) and an extra instance of the shelf object for each multiple shelf.
You need to add / remove manually if you adjust the number of shelves but then you can do a straight count of the shelf object without worrying about how many shelves each has.

Barry.

[Anonymous]

ispyridis wrote:

Barry wrote:
It is possible to use the 'Sum' and 'Flag' options to get a slightly better result - but I still don't think this is as clear as placing individual shelf objects and simply counting them each as one.

Barry.

I think If you move the quantity on the second column it will look better and make sense.

How about calling the self as a macro into the object that does the spreading and then scheduling the macro?
Would that work?

I did a small test, calling the same macro twice , in a "motherobject" but Archicad only counts the single "motherobject"... Just as Barry wrote!

[Anonymous]

It seems though, a good idea to be able to schedule macro objects. That way it would be like making a BOM for furniture or any other assembly. So the main object would be like an assembler with translation commands, multipliers and other controls and the macro objects just geomerty. I know that there are some old complex objects that are based on this philosophy and they were comming along with some list schemes. I haven't looked how they were working neither used the list schemes. But now that there is interest I look to it.

Thanks