Yes, yes and YES! Honestly, DIA support for Palm (not to mention Sony's hurried implementation) seriously lacked forethought. The different behavior on devices and the different events sent internally by the OS force the developer to program for about 10 different scenarios if he wants the program to act the same on different devices.
Personally, I've scrapped DIA support. It's a feature that gets used by less than half of users yet accounts for about 80% of my programming time. As wonderful as it is, no feature used by so few users is worth that much of a time commitment. Thanks, I feel better now. --- Timothy Kostka Temporarily Embittered Palm OS Developer "Paul Nevai" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi: > > Some applications remember their own DIA state and some don't. This leads > to > a total chaos. E.g., try switching between Memos [aka Memo Pad] and the > Launcher and DateBk5. It's like total chaos. The DIA keeps expanding and > collapsing w/o the user even touching the DIA trigger. > > Why can't there be a general rule which all apps would observe? > > I personally prefer if the DIA is always controlled manually [the TT5 does > that with the built-in apps] but I can live with any rule as long as it is > applied consistently. > > BTW, having played a lot withe the TT3, TT5, Treo 600, and Treo 650 > simulators, I appreciate my Tungsten C more and more despite all the > headaches it caused with that infamous MAC address bug. > > /PaulN > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
