I am in the datawindow, change a value, then click ENTER key.  From ue_down_key event, it immediately goes to losefocus event and my rowfocuschanging, rowfocuschanged events never end up getting called. 


Workaround:
Put an Instance variable (boolean) into the Item Changed event.
Init the value to false, set it to true at the top of the ItemChanged event.
In the LoseFocus event, check the flag. If FALSE, then trigger the ItemChanged event.

Later -

Olan

Greetings, Brian -

Is there a command button in the window that has the "Default" property checked? If so, the Enter keystroke is being redirected to that command button before the DWC receives the Windows WM_KEYDOWN message. Uncheck this command button property and make sure no other command buttons in this window have it checked, and you should get the behavior you are expecting.

Regards, John

Hi Brian,

Is this happening while debugging on the IDE, while running on the IDE, or is this also happening during compiled runtime?

Please try to do a Full Build and an Optimize to each library, then re-compile and test again. Do let us know if this worked for you.

Regards,

I checked other events and not seeing where other code is capturing the keystroke.

Here is info from logging that I added:

06-26-2020 15:30:03.226,Connection 3516239,d_rt_request_list,ue_down_key - line 8 - keyflags = 0
06-26-2020 15:30:03.226,Connection 3516239,d_rt_request_list,ue_down_key - line 9 - keyflags = 0
06-26-2020 15:30:03.226,Connection 3516239,d_rt_request_list,ue_down_key - line 10 - keyflags = 0
06-26-2020 15:30:03.227,Connection 3516239,d_rt_request_list,ue_down_key - line 573
06-26-2020 15:30:03.242,Connection 3516239,d_rt_request_list,losefocus

I am in the datawindow, change a value, then click ENTER key.  From ue_down_key event, it immediately goes to losefocus event and my rowfocuschanging, rowfocuschanged events never end up getting called. 

This is not 100% reproducible as it works fine for a while and then this behavior starts (not sure how or why).  Once this starts, only remedy is to re-start application.

This is a major issue that is holding us up from completing migration from PB 11.5 to PB 2019.  

Any other thoughts or ideas to try?

Thanks,

Brian

Check the events in both the parent window and the DW to see if there is code that captures the keystroke. Odds are good that such code exists and is causing the error you describe.