Bug #8711
TAB-STOP attribute wrong implementation for RECTANGLE, IMAGE and TEXT widgets
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
Related issues
History
#1 Updated by Vladimir Tsichevski 2 months ago
- Related to Bug #8673: Deduce the logic behind OE focus management and implement in FWD added
#2 Updated by Vladimir Tsichevski 2 months ago
In OE the TEXT
widget has the TAB-STOP
attribute (despite the official docs say otherwise), and RECTANGLE
and IMAGE
do not have this attribute.
The following code example:
DEFINE RECTANGLE r SIZE 10 BY 10. DEFINE IMAGE img &IF DEFINED(FWD-VERSION) &THEN FILE "/usr/share/icons/gnome/16x16/emotes/face-devilish.png" &ELSE FILE "Z:/test3820/deploy/client/img-up.png" &ENDIF . DEFINE VARIABLE txt AS CHARACTER VIEW-AS TEXT NO-UNDO. DEFINE FRAME outerFrame r img txt NO-LABEL WITH SIZE 80 BY 15. r:SENSITIVE = YES. img:SENSITIVE = YES. txt:SENSITIVE = YES. txt:SCREEN-VALUE = "qwerty". MESSAGE r:TAB-STOP img:TAB-STOP txt:TAB-STOP. r:TAB-STOP = YES. img:TAB-STOP = YES. txt:TAB-STOP = YES. ENABLE ALL WITH FRAME outerFrame. WAIT-FOR GO OF FRAME outerFrame.
demonstrates the following:
In OE:
- reading or writing the
TAB-STOP
for a rectangle or image causes an error message box. So, running the code results in 4 error boxes. - the
TEXT
widget is a validTAB-STOP
, so it is present in the frame field group, selected as the focus receiver at the start and highlighted.
In FWD:
- no errors is generated neither in conversion, nor in run-time. The
TAB-STOP
isno
for rectangle, andyes
for the text and image. - the frame field group is empty, the text widget has no focus on start, and does not receive focus on mouse click.
#3 Updated by Vladimir Tsichevski 1 day ago
Additional observation:
Unlike all other field-levels, the default value of TAB-STOP
attribute for a TEXT
is FALSE
.