My app works flawlessly on the PalmOS53 simulator, but on a real Tungsten T3, the users found that they can't exit the program with the Launcher button or get to the menu with the menu button.

The way my app works is it Enumerates the silk regions and stores them in an array. (Again, this works fine on the simulator.) If the user taps on an area of the screen that matches one of the silk buttons, the app passes the pen down onto the system, which then generates the vchrMenu or AppExit events. (Again, this works on the simulator.)

In real life, it appears to fail. The only easy possiblity that comes to mind is that on the real T3 the silkEnum function isn't working correctly and not giving the correct layout of the buttons. But unfortunately I don't have access to a real T3 to test.

Does anyone from PalmOne have an idea as to whether or not the T3 would correctly implement these functions, or if any differences from the Simulator might explain why users can't operate the silk buttons?

Thanks!
- Jeff



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

Reply via email to