Kbase P119027: Different toggle-box behavior between GUI and TTY client
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/09/2010 |
|
Status: Verified
SYMPTOM(s):
Different toggle-box behavior between GUI and TTY client
Applying the VALUE-CHANGED event on a toggle-box
Toggle-box is checked in TTY
Toggle-box is unchecked in GUI
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
CAUSE:
Bug# OE00132803
FIX:
Upgrade to OpenEdge 10.2B02 or later
This introduces the new -togboxfix client startup parameter, which allows selecting the behavior to apply for both GUI and TTY clients:
-togboxfix 1 : Do not change the toggle box's value on APPLY VALUE-CHANGED (the GUI behavior).
-togboxfix 2 : Change the toggle box's value on APPLY VALUE-CHANGED (the character behavior).
-togboxfix 0 (or any value other than 1 and 2) : Use the old inconsistent behavior.
As a workaround:
- Move any code in the ON VALUE-CHANGED trigger block for the toggle-box to a new internal procedure, and replace the trigger with an ON VALUE-CHANGED OF <toggle-box> RUN <new internal procedure>
- Replace code that applies the VALUE-CHANGED event in order to execute the trigger logic with a RUN statement for the new internal procedure.
- Replace code that applies the VALUE-CHANGED event in order to change the toggled state of the widget with an assignment to the <toggle-box>:CHECKED attribute.
If needed, use the SESSION:DISPLAY-TYPE attribute to test which output mode is currently in use in the running program.