For non-SESSION and non-APPLICATION properties, the property values can be set in several different places.  The order of precedence is:

  1. If no property value is defined the system default value will be used.  For colours and fonts this implies that the Windows Client’s current palette options are used as specified in the Applications Definition File.

  2. If a property value was assigned in the development environment, this becomes the default value.

  3. If a property value is assigned in a logic procedure when the object is not part of an active iteration cycle, this value become the default, and supersedes any default defined earlier. Such an amendment would normally be executed in the On Function Entry, On Cycle Entry, or Cycle Screen Mode event process points. However, it can be in any Logic which is executed before the iteration (of the cycle containing the object) begins.

  4. If a property value is assigned after the start of the iteration containing the object (in any Field Logic or File Logic) this will be a temporary setting and valid only for that cycle. The value will be restored to the default when the iteration is complete.
     

Default Logic is executed on mode change.

Comment on this topic

Topic ID: 510010