wxsqueak mailing list

[Cees de Groot]

On Tue, 22 Feb 2005 07:56:51 -0500, Rob Gayvert <rtg at rochester.rr.com>  
wrote:
>> Now that we're chatting. One issue seems to creep up when exposing the   
>> software to actual users over and over again: when an event is being   
>> processed, widgets are not disabled. So if you have a reasonably  
>> lengthy  operation, we've seen users getting impatient and starting to  
>> go into  'gremlin mode' (just clicking around), which prompts a message  
>> from wx  about max event stack depth reached and a subsequent goodbye  
>> from the  image.
>>
>> I'm plastering the software with WxWindowDisabler instances, but that   
>> doesn't feel like the final solution, somehow ;)
>
> Ah, real users can be such a pain. I haven't tried long delays like  
> this, so I'll have to see what's going on. At worst, we could add some  
> kind of WxReallyDisableItDammit primitive.
>
Or maybe always disable The Works while an event is being handled inside  
Squeak. But I don't know whether that'll work (although it's probably easy  
enough to try...)