El 15/12/2013 13:35, Paul McNett escribió:
On Dec 15, 2013, at 8:19, Ricardo Aráoz <[email protected]> wrote:
El 15/12/2013 10:36, Ricardo Aráoz escribió:
Done. It works!!!
So what are the options you wish to explore.
There's something strange going on with events in windows.
I am binding a dButton's KeyUp event. It would seem that the KeyUp event gets
fired when the button GETS focus and the event key is the key pressed in the
previous control (usually a Tab). In linux works as expected and the KeyUp
event will fire for keys pressed when the button has got focus (usually Tab or
shift+Tab), which allows me to keep track of what the user is pretending to do
when leaving the control.
Each platform has it's own event model. On windows as you've found the order
tends to be something like:
user clicks tab
key down for tab
got focus on new control
key up on new control
lost focus on old control
But also, nothing guarantees a particular order.
Good to know this.
Now supposedly the KeyDown event should fire when the user keys Tab.
This is not happening, the KeyDown event does not fire, but the
LostFocus does.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[email protected]
