WxListCtrl refresh issues

[Cees De Groot]

So it'd generally be safer for me to look into the deffered event
handling stuff is there's just the slightest bit of work to be done in
the processing routine.

I'll test with debugging on. I do have a lot of 'callback from unsafe
primitive' warnings in the log. Could that be related?

On 7/29/05, Rob Gayvert <rtg at rochester.rr.com> wrote:
> Cees,
> 
> I can't reproduce this with WxVirtualListCtrlDemo, so it's probably not
> a wx problem,
> and it certainly isn't something that your code should be responsible
> for.  I suspect it
> has to do with the generic callback mechanism. For one thing, it doesn't
> allow re-entrant
> calls (at least not yet -- I'm  working on generalizing the callback
> handling). So it's possible
> that a refresh event is arriving  at a bad time.
> 
> Are there any clues in wxsqueak.log? You might try setting "Wx
> debugCallbacks: true" and
> see if anything interesting shows up.
> 
> .. Rob
> 
> >Hi,
> >
> >I've noticed that (virtual) list controls have trouble refreshing.
> >More specifically, there are two places in my project where refreshing
> >doesn't work:
> >- When another window (modal dialog, for example) is moved over the
> >list, the contents of the list are erased where the dialog has been;
> >- In some circumstances, when I pop up a window with a listctrl and
> >programmatically fill it (through #setItemCount:).
> >In both cases, moving the window containing the affected list
> >refreshes it again. I'm not sure whether this is a Wx-level,
> >WxSqueak-level, or programmatic error (by me), but I find it hard to
> >believe my code can cause this...
> >
> >(haven't gotten around retrying the XRC issue with the subclassing - I
> >wanted to finish the widget and the panel thing worked nicely, so I
> >left it until after I get back from summer camp)
> >
> >Regards,
> >
> >Cees
> >
> >
> >
> 
>