>that doesn't solve the question of how we implement a work-around so our
>code that used to work when compiled under 3.1, that is now broken if we
>compile under 3.5, will work under all devices again.
Just grab the macro definition from your 3.1 sdk, and execute that code if
and only if you're on < 3.5. But make sure you use the API if you're on
3.5 or higher, so you'll keep working in the future.
Make it a routine in your own app if you want, called
myEvtSetNullEventTick, which checks the OS version and does the right thing.
> Why on Earth would Palm break functioning code like this??
The fundamental problem with the macro was that it tweaked a low-memory
global and thus was extremely fragile and impossible to improve. In short,
it was an ugly hack and never, ever should have been shipped, much less
documented.
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
