callback strangeness?
Cees de Groot
cg at cdegroot.com
Tue Mar 15 20:05:55 UTC 2005
On Tue, 15 Mar 2005 14:53:52 -0500, Rob Gayvert <rtg at rochester.rr.com>
wrote:
> With a virtual list control, #onGetItemImage: get called once for each
> item in the list each time that the list is displayed, so if the
> callback takes a significant amount of time this is going to make the
> GUI very unresponsive. I think you'd be much better off with some kind
> of asynchronous update to the list.
>
Yup. However, this is just the single list where network-wide search
results are displayed. Furthermore, in this particular case, the callback
took time because the network didn't return any results (it tries for 2
seconds) which indicates some data inconsistencies (IOW: shouldn't happen
in Real Life, at least not regularly).
But performance/responsiveness aside, any idea what causes the crash&burn?
More information about the Wxsqueak
mailing list