I used to run into that occasionally, so I always leave optimizations turned off until towards the end of the development cycle. A few years ago, before I started doing that, I would have suspected it.That's weird behaviour alright. Have you tested to see if it's a complier optimisation bug? (eg: in your eventloop, throw up an alert if the lstSelectEvent pops up, before passing it to frmHandleEvent.)
Actually, I figured out what it was. There was a duplicate list object exactly the same size as the one I was having the problem with. I must have created it accidentally in Constructor when first building the form. Since it was the same size, and in the same place, it was invisible.
Apparently OS 3.5 was treating penDown events as hitting that list, which was empty. Hence, no lstSelect events (there was nothing to select). OS 4.0 was treating penDown events as hitting the list I was tracking, and it had items, so it generated lstSelect events.
It's one of the weirdest things I've run into in six years of doing this. Once I eliminated practically every other thing, by stripping code out until there was almost nothing left, and it still didn't work, I figured it had to be something with the form itself. Sure enough...
Regards,
Steve Mann
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
