Project

General

Profile

Bug #3632

BUTTON and COMBO-BOX don't react on ENTER key

Added by Hynek Cihlar about 6 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:

History

#2 Updated by Hynek Cihlar almost 6 years ago

The simplest use cases can be used to reproduce this, uast/demo/demo_widgets.p will do.

As of trunk revision 11279, this is still an issue.

In Progress, opening up a COMBO-BOX list view, highlighting an item and pressing ENTER key should close the list view and select the highlighted item. In FWD pressing ENTER does nothing.

For BUTTON, when it is focused, pressing SPACEBAR should cause the CHOOSE event. In FWD pressing SPACEBAR does nothing.

#3 Updated by Hynek Cihlar almost 6 years ago

Hynek Cihlar wrote:

For BUTTON, when it is focused, pressing SPACEBAR should cause the CHOOSE event. In FWD pressing SPACEBAR does nothing.

Correction, both SPACEBAR and ENTER cause the CHOOSE event, however there is no visual feedback of the button being pressed in FWD.

#4 Updated by Eugenie Lyzenko almost 6 years ago

Task branch 3661a has been updated for review to revision 11281.

This is the fix for COMBO-BOX reaction on ENTER key pressing for opened drop-down window. In GUI mode we need to consider ENTER event as combo-box closer in addition to regular RETURN.

Continue with button SPACEBAR and ENTER key feedback regression.

#5 Updated by Eugenie Lyzenko almost 6 years ago

Only SPACEBAR key pressing has visual feedback in 4GL. ENTER key has nothing to be visible.

So we have the deviation for SPACEBAR only.

#6 Updated by Eugenie Lyzenko almost 6 years ago

The BUTTON widget regression has been fixed in 3661a revision 11282.

So far the task loos completed.

Also available in: Atom PDF