Bug #10699
Defining a trigger for just one part of the low-level DOWN-UP pair of mouse triggers doesn't disable the default mouse click behavior
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Delia Mitric 9 months ago
This is the testcase:
DEFINE VAR fill1 AS CHARACTER VIEW-AS FILL-IN NO-UNDO.
DEFINE VAR fill2 AS CHARACTER VIEW-AS FILL-IN NO-UNDO.
DEFINE FRAME f
fill1 AT ROW 1 COL 2
fill2 AT ROW 4 COL 2
WITH SIDE-LABELS 1 DOWN SIZE 50 BY 10.
// FILL1 TRIGGERS
ON ENTRY OF fill1 DO:
MESSAGE "IN ENTRY fill1: " FOCUS:NAME.
END.
ON MOUSE-SELECT-DOWN OF fill1 DO:
MESSAGE "IN MOUSE SELECT DOWN fill1: " FOCUS:NAME.
END.
ON LEAVE OF fill1 DO:
MESSAGE "IN LEAVE OF fill1: " FOCUS:NAME.
END.
// FILL2 TRIGGERS
ON ENTRY OF fill2 DO:
MESSAGE "IN ENTRY fill2: " FOCUS:NAME.
END.
ON MOUSE-SELECT-DOWN OF fill2 DO:
MESSAGE "IN MOUSE SELECT DOWN fill2: " FOCUS:NAME.
END.
ON LEAVE OF fill2 DO:
MESSAGE "IN LEAVE OF fill2: " FOCUS:NAME.
END.
ENABLE ALL WITH FRAME f.
WAIT-FOR CLOSE OF CURRENT-WINDOW.
Click on the second fill-in.
Progress results:IN ENTRY fill1IN MOUSE SELECTED DOWN fill2: fill1
ON MOUSE-SELECT-DOWN trigger alters the default click behavior of the mouse:
- the
LEAVEevent of fill1 isn't triggered - the
ENTRYisn't triggered for fill2 - the focus isn't changed (remains on the first fill-in)
This seems to be a quirk in Progress. The explicitly ON MOUSE-SELECT-DOWN trigger (even it is empty) modifies how a normal click bahaves.
To obtain the entire "click" behavior we need to explicitly put an "UP" trigger:
ON MOUSE-SELECT-UP OF fill2 DO:
...
END.
On the other side, if we run the testcase with FWD, these are the results:
IN MOUSE SELECTED DOWN fill2: fill1 IN LEAVE OF fill1: fill1 IN ENTRY fill2: fill1
(And the focus is changed)
#2 Updated by Delia Mitric 9 months ago
- Subject changed from Defining a trigger for just for one part of the low-level DOWN-UP pair of mouse triggers doesn't disable the default mouse click behavior to Defining a trigger for just one part of the low-level DOWN-UP pair of mouse triggers doesn't disable the default mouse click behavior