Difference between revisions of "Class Browser"
(→Common context menu) |
(→Common context menu) |
||
| Line 14: | Line 14: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| − | ! | + | ! Menu !! Purpose |
|- align="center" | |- align="center" | ||
| Navigate To || Opens the navigation menu | | Navigate To || Opens the navigation menu | ||
Revision as of 20:58, 22 January 2013
Contents
Purpose
The Class Browser is designed to display and edit UBIK® objects in a hierarchical manner. It is also meant to be the superior of all other controls and the only one where at least one instance of it is actually mandatory in a UBIK® Studio session. So it can be considered as the root of object manipulation in UBIK®.
In addition, it makes use of Namespaces and uses them for structuring the displayed objects even further.
Basics
Icons and Tooltips
Depending on the current View Style, the control display different types of UBIK® classes. Each major class type is associated with a unique icon, in order to provide a visual distincton of the class types. However, these icons can be replaced by more specific ones during the customization process, which means that it is not a reliable indicator if an object is of a certain type. In contrast, hovering with the mouse over a tree node will bring up a Tooltip-Text, showing you the system type of the respective object.
Clicking a node with the right mouse button will bring up a standard context menu for each node, except Namespaces. Depending on the View Style there will be different options, however, all nodes will at least show the following menu items:
| Menu | Purpose |
|---|---|
| Navigate To | Opens the navigation menu |
| Delete | Deletes the object |
Toolbar
View Styles
The Class Browser has three different View Styles, each of the providing different views and functionality.
Hierarchical
In this View Style, the Derivates relation from each MetaClass deriving directly or indirectly from BaseClass will be evaluated.
Inheritance
In this View Style, Inheritance relation of all MetaClasses will be evaluated.
Content
In this View Style, the Instances of all MetaClasses will be evaluated.
