callback strangeness?

[Cees de Groot]

> Hmm, this sounds like a different problem. To verify that it's not a  
> problem with #setCallbackFlags, try setting "Wx debugCallbacks: true".  
> This will write some callback detail to the file wxsqueak.log.  If you  
> see a line with "...setCallbackFlags...<your class>...flags=0" then  
> there is still a problem. If the flags are not zero, the problem is  
> likely elsewhere.
>
Nothing like that. The lines are all like:

18:39:02: : wxGenericCallback, cls=WxListCtrl, method=onGetItemImage:,  
type=0
18:39:02: : callback: cls=WxListCtrl, selector=onGetItemImage:
18:39:02: : callback argTypes: #(WxListCtrl SmallInteger)
18:39:02: : callback: args=#(DGVPluggableList[16r14A6A18] 1)
18:39:02: : wxGenericCallback, cls=WxListCtrl, method=onGetItemAttr:,  
type=24
18:39:02: : callback: cls=WxListCtrl, selector=onGetItemAttr:
18:39:02: : callback argTypes: #(WxListCtrl SmallInteger)
18:39:02: : callback: args=#(DGVPluggableList[16r14A6A18] 2)

However, I just realized that the p2p search sends global references, not  
actual objects, in some cases. Reference resolution times out after two  
seconds, so that could be the cause of this. I'll investigate more...