Problem:        A pen tap on a Text or Lookup control generates 2 OnPenDown events on PocketPC, instead of a single event.  This does not affect the PalmOS platform, nor does it affect other control types on PocketPC.

Solution:        There is no solution to this problem at the current time.  If you need to track the number of pen taps as a count, or otherwise want to trigger a pendown script only once for these unwanted double-tap events, you can use the following workaround:

1. Use the PenTapInControl global script to determine if the tap was within a text or lookup control, or otherwise.
2. If the tap was in a text or lookup control, toggle a global flag variable (eg. gFlagDoubleTap = not gFlagDoubleTap).
3. In the OnPenDown script, check the gFlagDoubleTap var and only take action when gFlagDoubleTap = false.
4. Set gFlagDoubleTap = false in AfterOpen.  When the first pen down event fires, gFlagDoubleTap will be set True, and the script action will not fire because gFlagDoubleTap = True.  When the second pen down event fires, gFlagDoubleTap gets set back to false, and the script action will proceed.  Pen taps on other controls or on the form will not set gFlagDoubleTap = True, therefore they will execute the script on the first tap.

Status:        OPEN        This bug has not been resolved yet.

Keywords:        OnPenDown, OnPenUp, pen, tap, double-tap, GetPenStatus, PenTapInControl

BugID:        SF-00353

KB ID: 10057 

Updated: 2007-06-22

Satellite Forms KnowledgeBase Online

Satellite Forms Website Home