Guidelines for Subclassing Objects
When subclassing objects, consider these guidelines:
- When you subclass an object, the objects owned by the source object get
subclassed, not the objects associated with the source object.
For example, when you subclass a block, the graphic text labels for items
in the block are not included. Graphic text is owned by the canvas on which
it appears. To subclass graphic text, you must subclass the desired canvas.
- When you subclass an object across modules, both the source module and the
target module must be open, and the source module must already have been saved,
either to the file system or the database.
- Use caution when deleting source objects; deleting a source object will
break the links to any subclassed objects.
- Use caution when you modify the name of a source object.
- You can interfere with the functionality of the application when you change
the name of an item that is referenced in trigger or program unit code, or
that relates to a database column.
- Use caution when overriding complex values (e.g., List elements).
- Modifying a program unit that has been subclassed will require the subclassed
program units to be recompiled.
- You must use the Property Palette to modify subclassed code. Modifying subclassed
code in the PL/SQL Editor will break the link to the source object.
Related topic
Subclassing an object