Skip to content

Latest commit

 

History

History
34 lines (20 loc) · 2.22 KB

style-object-editor.adoc

File metadata and controls

34 lines (20 loc) · 2.22 KB
Raw

Style Object Editor

Table of Contents

1. Overview

The Style Object Editor works exactly as the VID Object Editor works. Except that it controls facets for all instances of the underlying style. By leaving Style Object Editor and the VID Object Editor open at the same time you can see where facet values are set. See: VID Object Editor and Styled Facets

2. Opening the Style Object Editor

You can open the Style Object Editor one of four ways:

  1. Through the VID Object Editor by clicking on the Edit Style button as highlighted below: opening soe via voe

  2. Holding the SHIFT key down and pressing the middle mouse button while hovering over a GUI Object

  3. Pressing the Control + Shift + Tilde keys while hovering over a GUI Object

  4. Highlighting a portion of a style code in the VID Code Editor and pressing Control + Tilde keys

3. Styled Object Behaviour

When dealing with cascading VID styles, the default Red behavior is that any action (like on-click and on-change etc.) that a parent has will be completely overridden by a child if the child has the same action defined.

When using Direct Code, however, you are able to see the existing style action and append and/or change the style action as the overriding behavior. This allows you to use the style as a starting template and build upon it without having to rewrite the original style behavior.

When inserting a cascading style (styles containing parents and children) if there is a setup-style block contained anywhere in the family tree the youngest setup-style block or setup-style closest to the style being inserted is used.

When dealing with a cascading style the youngest object takes precedence. IE. If you insert a parent/child/grandchild object you can’t really run the parent or grandparent style objects separately. This needs to be considered when designing cascading styles.

Let’s say you create a custom field style like this : parent-field and a child-field . The child field is the usable portion of this style and will be the one listed in the style catalog. The parent-field is not accessible in any way other than through the child-field.