Kbase P20523: Setting the SENSITIVE attibute of a widget to true sets the MODIFIED attribute of that widget to fal
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/19/2008 |
|
Status: Verified
SYMPTOM(s):
Setting the SENSITIVE attribute of a widget to true sets the MODIFIED attribute of that widget to false
Using <handle>:SENSITIVE = TRUE syntax
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
CAUSE:
This is expected behavior, although not very intuitive.
Progress development will not change this behavior as it may affect applications that rely on the current functionality. For example:
- A field/fill-in is enabled (ie: SENSITIVE = TRUE)
- that field s modified (:MODIFIED = TRUE),
- that field is disabled (set :SENSITIVE = FALSE),
- that field is saved. <-- If this was done here then the current functionality could be valid.
- field is immediately enabled (set SENSITIVE = TRUE, :MODIFIED becomes FALSE)
FIX:
Manually set the MODIFIED attribute of the field to true after setting the SENSITIVE attribute to true