Folks, We have a large application with many forms. It's been deployed for several months, and is being used every day by "unskilled" workers. The application is running on a variety of models: IIIe, Symbol 1500s, Symbol 1700s, m100's, and pretty much anything else that is 3.0 or greater. The app is quite stable, but there have been occasional (rare) reports of a very odd occurence. When in the field, workers have reported that they've encountered a situation where the "screens start flashing from form to form" ... just like you'd expect when a horde of gremlins is loosed in the emulator. Usually this activity stops after a bit, but I think that users have had to do resets in other instances. Though the effect isn't readily reproducible, the Palms are being used by some operations to gather data via the serial port from "machines" The problem may be arising primarily while this protocol is engaged. When this first occurred, an inspection of the Palm (a Symbol 1700 in this case), revealed some nasty scratches across the touch screen ... right where our form's navigation buttons are placed. The unit couldn't even be effectively calibrated. We assumed that the touch screen was "weirding out" and sending events to the application ... resulting in repeated navigation between forms. The most recent incident occurred today (also a Symbol 1700) ... but the unit seemed in perfect condition. Has this sort of thing happened to anyone out there? Are there any well understood circumstances that can result in this "stuck key" sort of behavior on a touch screen? My thanks in advance .... kjq -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
