Looking at the source code, I'm now recommending the use of CtlHitControl.
Not only does it save you the work of setting up the ctlSelectEvent, it does
a very thorough job of it, setting some things that are normally left out,
such as event.penDown event.screenX, and event.screenY.

On a more general note, the fact that form objects are referred to in three
different ways (pointer, ID, index) definitely makes for a messy API. There
are performance differences between these alternatives, so there is some
reason to have them, but it still seems overly complicated to me.
-- 
Peter Epstein

-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to