Re: [wxperl-users] 0.26 flicker notes

[Mark D. <mar...@zn...>]

Hi,

I think it would depend what you wanted to do.
My understanding, though untested, is that Wx::Yield would allow all 
events to be processed - including re-entering  the event code you are in.
$this->Refresh;
$this->Update;
would not allow re-entry into your button click event until the current 
iteration had completed.

My thought is that Wx::Yield is more suitable for some long running 
process where you want to have the chance to respond to user requests 
like 'cancel' or 'pause' periodically.

My understanding of this particular problem was that it was visually 
unpleasing to have the button not refresh until the resulting action had 
completed - so Refresh/Update seemed the correct solution.

But it is always good to know that there is an aternative approach such 
as Wx::Yield - as you may want the behaviour that gives in some instances.

I suppose that the ideal solution would be to create your own button 
class, respond to the click events in that with a refresh of the button, 
then propagate the event to your handler with ->Skip(1);

Regards

Mark


Christian Renz wrote:
>>   $this->Refresh;
>>   $this->Update;
> 
> 
> Wouldn't it be better to use Wx::Yield instead?
>