All Sedona components provide the identical “Guide on Target” Help ord, instead of unique ords by kitName
-componentName
. Therefore this section describes the single common property implemented by all Sedona components:
The Meta property is available in property sheet of any Sedona component, with Figure 48 showing an example.
Meta stores two different pieces of information:
Groups
Four component groups are available, numbered 1 through 4. Each component must belong to at least one group, and can belong to all four if desired. Membership in a group determines what permissions an app user has for that component, according to that user’s permissions map.
For related details, see Sedona User Manager.
Position
The x and y coordinates of the component’s upper-left corner’s glyph (shape) in the wire sheet view of its parent container. Integer values are used, which correspond to grid increments on the wire sheet, starting with 0, 0 at the wire sheet’s top-left corner.
A component’s position values automatically track any “drag” movement of its shape on a wire sheet, and thus typically are not directly edited in the Meta dialog (Figure 48).
Storing the position of the components in an app maintains wire sheet layouts, which is essential when working with collections of components and the links between them.
Copyright © 2000-2014 Tridium Inc. All rights reserved.