Simon Arrowsmith wrote:
> traceback suggests to me that wxEndBusyCursor is involved, which
> sounds vaguely familiar, but I can't find anything in the 2.4 to 2.5
> migration guide.
You didn't state which platform this happens on. There is definitely
a bug on wxGTK that wxBeginBusyCursor (and I assume EndBusyCursor)
re-invoke the event loop (presumably via Yield).
That'll be the one. (GTK1.2 on Linux.)
···
From: Roger Binns [mailto:rogerb@rogerbinns.com]