Problem with LEAVE Trigger

sebouh181

New Member
Hello...

I have a strange problem regarding triggers.

I have a very simple window that contains a Fill-in (cText) and a browse (mainBrowse).

cText has a LEAVE trigger that contains the following.
DO:
APPLY "VALUE-CHANGED" TO mainBrowse.
APPLY "ENTRY" TO mainBrowse.
END.
The two triggers are empty, they do not contain any code.

When I click inside cText (ENTRY on cText) and then click on the browse (LEAVE on cText, ENTRY on mainBrowse), the VALUE-CHANGED is executed after the ENTRY, and the LEAVE trigger no longer works, that is if I do the above operation a second time it does nothing. Furthermore, if the window was called from another parent window through a button, that button's "CHOOSE" trigger no longer works.

The problem is fixed by changing the order of the APPLY, like this
DO:
APPLY "ENTRY" TO mainBrowse.
APPLY "VALUE-CHANGED" TO mainBrowse.
END.

But what I need to know is, if there are any explanations for this behavior?

Thanks in advance
 
Apparently the problem is due to the mouse events.
if i add a "MOUSE-SELECT-DOWN" event to the browse with nothing in it, (which means disabling the trigger), everythin works fine.
DO:
/* any comment */
END.

Is there a workaround to this problem, so I wouldn't have to create this empty event for each and every browse?

Is this a known problem/bug in Progress?
 
Back
Top