Guidelines for Creating Object Groups
When working with object groups, consider these guidelines:
- Dragging a block into an object group implicitly includes all objects that
are owned by the block (items, triggers, relations). However, objects owned
by the block do not appear under that block in the List of object group children.
- Only top-level objects can be included in an object group.
- Objects owned by blocks cannot be independently placed in an object group.
This includes items, item-level triggers, block-level triggers, and relations.
These objects cannot exist independently of the block in which they were defined.
To include these objects in an object group, you must include the block itself
by dragging the block object into the object group in the Object Navigator.
- The objects in a group must all be defined in the same module; you cannot
place objects from two different forms in the same object group.
- An object group cannot contain another object group.
- When an object in an object group is deleted from a module, it is removed
from the object group automatically.
- Deleting an object group from a module does not delete the objects it contains
from the module.
- Object groups do not store copies of the objects they contain, but rather
pointers to the objects; defining object groups does not increase module size
significantly (unless the object group is subclassed).
Related topics
About object groups
Creating an object group