Okay, at least now I know that the incorrect bounds during drawing while highlighting is a bug in the table code, not mine. Assuming that the fix involves passing the correct bounds in _and_ highlighting the full height of the cell, then my code as it is now will start working when the fix appears. Presumably the Launcher app can then be simplified so that it can rely on table semantics rather than doing highlighting by hand. ;-)
I was already processing penDown/penMove/penUp events for other reasons, so driving highlighting off them won't be hard - provided I figure out why screen draws don't show up on the screen except when done inside my cell draw callback. Thanks, Mark Peters "Peter Epstein" <[EMAIL PROTECTED]> wrote in message news:79942@palm-dev-forum... > > [...] > > You have pointed out a bug in the table code (as well as the obvious > annoying limitation that was fixed in 4.0). A custom table item is given the > full row height when it is asked to draw itself, but only highlights itself > if the tap is within the top 11 pixels. That inconsistency should be > corrected. Also, the documentation is lacking in that it doesn't spell out > what the height of each item style is. > > [...] > > For that, you need to write your own EvtGetPen loop. I think you'll find > this isn't actually that hard once you've seen how the table code does it. > -- > Peter Epstein > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
