I thought I had found a different solution, which was to register for the 
sysNotifyProcessPenStrokeEvent and to handle it if the stroke was within a 
silkscreen button (determined using EvtGetPenBtnList).  But then I noticed...   

On the TX and T3, when the user holds down the pen over one of the silkscreen 
buttons, the OS pops up a list letting the user choose which program the button 
should launch.  And when this happens, I do not get the pen stroke notification.

Do you (or does anyone else) know if the eventDequeued approach handles this 
particular situation?

Argh.



-- 
For information on using the ACCESS Developer Forums, or to unsubscribe, please 
see http://www.access-company.com/developers/forums/

Reply via email to