Hi Eric,

Firstly, I rather like the ->{TERM} idea of your application. The concept has a sort of retro feel to it. Very cool. I might try to build something using this idea. (I'd really like Linux smartphone with a just a command prompt on it! I'd type "call somebody" and it would dial the number. Has a very "post Snowden" feel to it.)

On 11/11/14 10:31, Erik Colson wrote:
Playing a little more with Yield. It seems that Yield allows the user to
click on buttons again, while the routine is still executing. So the
code produces an error:

perl(40521,0x7fff76d6a300) malloc: *** error for object 0x7fff5eb01280: pointer 
being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

So that tells I need to keep to track of the user interupting things or
something else, which might be more user friendly in most cases..
Yes, it's true. I had a number of bugs because Wx::Timer started running again.

You should probably do a

     $addTxtBtn->Disable();

after the click.
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.

Have fun,

Regards

Steve.

Reply via email to