Steve Cookson <steve.cook...@sca-uk.com> writes: > You should probably do a > > $addTxtBtn->Disable(); > > after the click.
yep, but in the real app there are lots of things I'd need to disable :( >> However, I figure in this usage I'd better split my routine and add the >> loop as separate calls to a specific function. The calls would then be >> trigered by adding them to the event loop. > In fact, you probably wouldn't need the Yield(), if you had a > Wx::Timer running and doing the work for you. Yep, I'm thinking about using a Timer for this stuff. Or I could create a class which would hold all the stuff to be done in a queue. Then after each pass control goes back to the MainLoop which updates the screen. But that would also give the user the ability to click.. So, in both cases (with the timer or the specific task container class) I'd need to keep track of a task being run and add a check in every user event handler to see if a task is running and therefor not allowing user events. Sounds like a no-go to me :( Other ideas ? -- erik colson
