Hi there,
I hope you don't mind me asking a question every day. ^^
As I've read in another thread, there is only one event handled at the time.
But where is decided in which order the events are handled, if an interaction triggers more than one?
(In my case, EVT_BUTTON and EVT_KILL_FOCUS - I want the button event to be handled first.)
Regards,
jellyfish
Order of events? Topic is solved
...hmh, not so good news. Thank you very much, however.
So maybe the KILL_FOCUS event wasn't the best choice for my problem. I guess there is no such thing as waiting in an event handler for another event?
Regards,
jellyfish
Edit: I've found wxApp::FilterEvent and wxApp::Pending ... is there anywhere an example how to use wxApp outside OnInit()?
So maybe the KILL_FOCUS event wasn't the best choice for my problem. I guess there is no such thing as waiting in an event handler for another event?
Regards,
jellyfish
Edit: I've found wxApp::FilterEvent and wxApp::Pending ... is there anywhere an example how to use wxApp outside OnInit()?
-
- In need of some credit
- Posts: 2
- Joined: Mon Feb 26, 2007 4:33 pm
Why not doing a Finite State Machine
Hello,
do a FSM and you will do the behaviour of your system, and you will change state on event receptions.
Sincerely
do a FSM and you will do the behaviour of your system, and you will change state on event receptions.
Sincerely