Hello, I am working on a little app that needs to capture taps anywhere on the screen to change to the next piece of information (it is intended to be used in a car while driving, so the goal is to be as generous as possible with the active area of the screen).
That is all working great by capturing the penUpEvent, except that I seem to be getting additional pen up events for all the menus and for the about box OK button. Here's a log that shows the problem. I opened the menu (by tapping the title bar), selected the about option which brings up a dialog window, then clicked OK in there to close the about dialog. Notice the additional penUpEvent at the end though: 1.203: <- EvtGetEvent: frmTitleEnterEvent ID: 1 1.219: <- EvtGetPen: screenX=26, screenY=4, penDown=1. 1.234: <- EvtGetPen: <<<eliding identical events>>>. 1.250: <- EvtGetPen: screenX=26, screenY=4, penDown=0. 1.250: <- EvtGetEvent: frmTitleSelectEvent ID: 1 1.250: <- EvtGetEvent: keyDownEvent Key:0x105 (vchrMenu), Modifiers: 0x0008 1.250: <- EvtGetEvent: menuOpenEvent RscID:0, cause:0 1.250: <- EvtGetEvent: keyDownEvent Key:0x105 (vchrMenu), Modifiers: 0x0048 1.281: <- EvtGetEvent: winExitEvent Enter: 0003A294 Exit: 00004AA4 Exit Form: "Directions" 1.281: <- EvtGetEvent: winEnterEvent Enter: 0003A294 Exit: 00004AA4 Exit Form: "Directions" 1.281: <- EvtGetSysEvent: penUpEvent X:26 Y:4 1.281: <- EvtGetEvent: penUpEvent X:20 Y:-10 4.109: <- EvtGetSysEvent: penDownEvent X:33 Y:40 4.109: <- EvtGetEvent: penDownEvent X:27 Y:26 4.125: <- EvtGetPen: screenX=27, screenY=26, penDown=1. 4.140: <- EvtGetPen: <<<eliding identical events>>>. 4.187: <- EvtGetPen: screenX=27, screenY=26, penDown=0. 4.203: <- EvtGetEvent: winExitEvent Enter: 00004AA4 Exit: 0003A294 Enter Form: "Directions" 4.203: <- EvtGetEvent: winEnterEvent Enter: 00004AA4 Exit: 0003A294 Enter Form: "Directions" 4.203: <- EvtGetEvent: menuEvent ItemID: 3001 4.250: <- EvtGetEvent: winExitEvent Enter: 00004CC0 Exit: 00004AA4 Enter Form: "About Directions" Exit Form: "Directions" 4.250: <- EvtGetEvent: winEnterEvent Enter: 00004CC0 Exit: 00004AA4 Enter Form: "About Directions" Exit Form: "Directions" 4.250: <- EvtGetSysEvent: penUpEvent X:33 Y:40 4.250: <- EvtGetEvent: penUpEvent X:31 Y:-51 5.609: <- EvtGetSysEvent: penDownEvent X:24 Y:147 5.609: <- EvtGetEvent: penDownEvent X:22 Y:56 5.609: <- EvtGetEvent: ctlEnterEvent ID: 12004 5.625: <- EvtGetPen: screenX=22, screenY=56, penDown=1. 5.640: <- EvtGetPen: <<<eliding identical events>>>. 5.656: <- EvtGetPen: screenX=22, screenY=56, penDown=0. 5.656: <- EvtGetEvent: ctlSelectEvent ID: 12004 On: 0 5.656: <- EvtGetEvent: winExitEvent Enter: 00004AA4 Exit: 00004CC0 Enter Form: "Directions" 5.656: <- EvtGetEvent: winEnterEvent Enter: 00004AA4 Exit: 00004CC0 Enter Form: "Directions" 5.656: <- EvtGetSysEvent: penUpEvent X:24 Y:147 5.656: <- EvtGetEvent: penUpEvent X:24 Y:147 I would have thought that the button processing code would have absorbed the penUpEvent when it generated the ctlSelectEvent. Have I missed something here? Any ideas? At the moment, I have a nasty hack in place that causes the main application to skip a single penUpEvent anytime a menu was opened, but I'm sure that there must be a better way. I have searched in Google, Falch.net and various other places for anything that explains how to deal with this, but not seen anything. Thanks in advance, John... PS Sorry if this appears twice; I tried replying to the digest from yahoogroups/egroups but it was bounced with instructions that said I should send it to the address I had just sent it to :-( ===== Rate Corporate America at http://exec-ratings.bluedonkey.org __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
