Helix views allow data rectangles to be shaded to indicate whether the data seen is a default or an invalid value. These features are controlled by the Shade Defaults and Shade Invalid Fields menu selections found in the √ menu. They are both active by default.
When Shade Defaults is active, defaulted fields are indicated by a light dot pattern overlay. (See the example below.) Defaulted fields are seen when a data rectangle contains both a field and an abacus, and the current record has not yet been entered. For a record that has been entered, presence of defaulted fields indicates that the field is currently undefined, and that replacing the record will put the default into that field.
When Shade Invalid Fields is active, defaulted fields are indicated by a dark dot pattern overlay. (See the example below.) Invalid shading indicates that the contents of a data rectangle (whether already entered or not) do not meet the current validation criteria for that field. New data can not be entered until it meets validation criteria. In the case of previously entered data that is now considered invalid, the invalid data can be left in the record as long as it is not modified. Any change to the field will trigger the validation, requiring it to meet the current criteria.
The QuickDraw patterns that are used in Classic Helix applications are not available in OS X, so new forms of shading are used to indicate these states. The tables below show the effect of the Shade Defaults and Shade Invalid Fields options in Classic and OS X Helix applications.
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
To every rule, there must be exceptions. Flag fields that display as checkboxes or radio buttons do not show shading effects. Picture fields also do not show shading effects.
Document and Picture fields can not be validated, so there is no invalid field shading option available.
Optimization of Lists Using the Shade Invalid Fields Command