Kbase 13462: V7 SCREEN-VALUE and actual widget value may conflict
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
V7 SCREEN-VALUE and actual widget value may conflict
The following behavior is encountered in Version 7 for MS-Windows and
is resolved by Version 8.0A and later releases.
In working with widgets, it is possible to change the way a widget
appears on the screen WITHOUT affecting the :SCREEN-VALUE attribute.
In other words, a RADIO-SET might show "Item 3" to be selected when
"Item 1" is the actual :SCREEN-VALUE that's stored.
This happens mainly when you have a FILL-IN that does validation ON
LEAVE and puts you back in the FILL-IN if the validation fails. If
you attempt to leave the fill-in under these conditions by clicking
the value on a radio-set, then you'll be able to change the way the
radio-set looks on the screen, but the radio-set's :SCREEN-VALUE will
remain as though you never got there (due to the fact that the
FILL-IN's validation steered you right back.)
This is not something PROGRESS can fix, since it is traceable back
to the way Windows stacks events before passing them on.
Updated 29-SEP-95:
In Version 8.0A and later, the :SCREEN-VALUE attribute is maintained
in sync with the screen visualization, but there is still the chance
that the radio set value will be changed by the mouse click without
firing the VALUE-CHANGED event on the object. This will occur if the
radio set doesn't receive focus, as in the above example in which
the LEAVE trigger returns focus to the fill-in based on validation
test failure. This behavior cannot be modified at present. The
window system changes the screen value of the object before the LEAVE
trigger fires. This will also occur with toggle boxes, selection
lists and sliders.
Progress Software Technical Support Note # 13462