Bug #3
F4 in 2nd interaction causes cursor to be positioned outside a valid input field
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
History
#1 Updated by Greg Shah about 12 years ago
Originally reported by SVL on 12-31-2010.
This is a UI bug. The cursor is positioned outside a frame (or over a field that does not have input). The only way to workaround it is to use side-labels.
Testcase attached (out-of-field.p):
def temp-table tt
field f1 as integer
field f2 as char.
create tt.
tt.f1 = 1.
tt.f2 = "2".
form tt.f1 skip tt.f2 with frame f1.
message "press F1 then F4".
repeat transaction:
update tt.f1 with frame f1.
update tt.f2 with frame f1.
end.