Yes, we make no assumptions about the up or down order of the callback. I
know that the problem does not specifically lie in the callback as I have
placed breakpoints all over the callback function and watched the items
being drawn to the screen. Every item is drawn correctly to the listbox by
the callback function. The point at which things are erased in the listbox
is between the final iteration of the callback function and the return of
the calling listbox function to the code following it. I should probably
state that it's not only the items getting erased. It's also the scrollbars
and pretty much anything else that was drawn into the listbox.
Thanks,
Michael Ryan
"Scott Johnson (Bellevue)" <[EMAIL PROTECTED]> wrote in message
news:29832@palm-dev-forum...
>
> > From: Michael Ryan [mailto:[EMAIL PROTECTED]]
> > we use a simple callback function to simply draw items to the listbox
> > In Palm OS 3.5 we have a strange problem where just after the callback
> > function is done all the listbox drawing functions will randomly erase
> > We only have this problem with OS 3.5. All the other OSes work
>
> Well, the big change in 3.5 is that it can call your callback much more
> often than before. In particular it calls it to highlight and unhighlight
> the selected item, compared to pre-3.5 where the OS would just invert the
> pixels on screen. Are you sure your callback handles this correctly?
Does
> it make any assumptions about the draw calls coming in top-to-bottom row
> order? That would not be a safe assumption.
>
> (Just a few guesses.)
>
> -slj-
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
