Create sub objects in custom GDL objects (Hierarchical ArchiCAD Elements)

[Lucien]

Hello everyone,

We have created various logistics elements, such as conveyors, for our work as architects and logistics planners. In order to use these objects for BIM coordination, provisions for spaces were created within the objects. I would now like to output these two components as separate objects (see image 1), as it is possible with hierarchical elements like curtain walls, stairs and railings (see image 2).

Unfortunately, it is currently not possible to create sub-objects for custom GDL objects. I would be pleased if this could be added as a feature.

Image 1

Image 2 (Source)

Cheers,

Lucien

[NBGheikki]

I made a duplicate of basically this request, and asked it to be deleted. To add to this wish, here's my request:

Many times I've had situations where it would have been great if I could have used something like CALL in an object to create another, 'virtually real' object that would be visible in schedules. The virtual objects wouldn't have to be editable outside the parent object.

For example, if I had an object to create auditorium seating parametrically, it would "CALL{2}" or "CALL_INSTANCE" the chairs so that they could be listed in a schedule alongside similar chairs created individually, or if I had an object to create kitchen modules, the relevant subelements (ovens, cupboards, fridges) would show neatly in schedules. Different types of element-based structures would be possible, helper objects to spread objects in all sorts of patterns, etc, etc.

Similar results can be achieved using COMPONENT lines, but component listings aren't very sexy compared to schedules. I expect there might be all sorts of technical problems that could make this hard to implement, but I have the privilege of not knowing what is impossible... On the other hand AC already has some functionality that feels reminiscent of this: Stairs, Curtain Walls, and Railings are all objects that are composed of subelements that have their own life. Maybe this existing logic could be leveraged to implement this?

[NBGheikki]

Many times I've had situations where it would have been great if I could have used something like CALL in an object to create another, 'virtually real' object that would be visible in schedules. The virtual objects wouldn't have to be editable outside the parent object.

For example, if I had an object to create auditorium seating parametrically, it would "CALL{2}" or "CALL_INSTANCE" the chairs so that they could be listed in a schedule alongside similar chairs created individually, or if I had an object to create kitchen modules, the relevant subelements (ovens, cupboards, fridges) would show neatly in schedules. Different types of element-based structures would be possible, helper objects to spread objects in all sorts of patterns, etc, etc.

Similar results can be achieved using COMPONENT lines, but component listings aren't very sexy compared to schedules. I expect there might be all sorts of technical problems that could make this hard to implement, but I have the privilege of not knowing what is impossible... On the other hand AC already has some functionality that feels reminiscent of this: Stairs, Curtain Walls, and Railings are all objects that are composed of subelements that have their own life. Maybe this existing logic could be leveraged to implement this?

[NBGheikki]

Many times I've had situations where it would have been great if I could have used something like CALL in an object to create another, 'virtually real' object that would be visible in schedules. The virtual objects wouldn't have to be editable outside the parent object.

For example, if I had an object to create auditorium seating parametrically, it would "CALL{2}" or "CALL_INSTANCE" the chairs so that they could be listed in a schedule alongside similar chairs created individually, or if I had an object to create kitchen modules, the relevant subelements (ovens, cupboards, fridges) would show neatly in schedules. Different types of element-based structures would be possible, helper objects to spread objects in all sorts of patterns, etc, etc.

Similar results can be achieved using COMPONENT lines, but component listings aren't very sexy compared to schedules. I expect there might be all sorts of technical problems that could make this hard to implement, but I have the privilege of not knowing what is impossible... On the other hand AC already has some functionality that feels reminiscent of this: Stairs, Curtain Walls, and Railings are all objects that are composed of subelements that have their own life. Maybe this existing logic could be leveraged to implement this?

[NBGheikki]

Another obvious use case would be windows. Despite being one object, they usually contain subelements that would be useful to list separately, like window sills, casings, even handles.