The class inheritance hierarchy
A USoft web application contains Page classes and Control classes. Each Page and each Control of a runtime application is an instance of a class. The behavior and (if applicable) the look of a runtime instance depends on:
•The structure of objects and contained objects that the class contains.
•The properties of each of these objects.
You can inspect the structure of object and contained objects in the Object Tree. You can inspect and change the properties of each object in the Property Inspector.
To make classes manageable, they are structured in inheritance hierarchies. If a class C2 is a child of a class C1 in such a hierarchy, it is called a subclass of C, and it inherits from C1:
•All the objects and the entire object structure contained in C1, whether these objects were included at the level of C1 itself or for some ancestor of C1;
•All the property settings for all these objects, whether these settings were made at the level of C1 itself or for some ancestor of C1.
The level from which a specific property setting is inherited is displayed in the right-hand column of the Property Inspector.
If you have set a property to a special local value, but you want it to revert to the value it would normally inherit, you can press the Re-Inherit button in the Property Inspector.
Do not confuse the class inheritance hierarchy with the object containment hierarchy:
•The term "class" is associated with the inheritance hierarchies shown on the Page and Controls tabs of the catalog.
•The term "object" is associated with the containment hierarchy, which is shown in the Object Tree.