nsedona-SedonaComponent (anyKit:anyComponent)

 Represents any Sedona Framework component. All Sedona Framework components provide the identical “Guide on Target” Help ord in Workbench, instead of unique ords by kitName-componentName. Therefore this section describes the single common property implemented by all Sedona Framework components:Meta.

NoteRefer to the vendor’s documentation for any Sedona Framework device for specific details on Sedona components used in custom kits, and also the Sedona Framework Developer’s website for details on components in open source kits. At the time of this document, the URL for this API documentation is: http://www.sedonadev.org/doc/api.html

Meta

The Meta property is available in property sheet of any Sedona Framework component, with Figure 80 showing an example.

Figure 80. Meta property example in Sedona component


Meta property example in Sedona component

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 80).

    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.