> 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.
But the structure that the macro tweaks doesn't exist in the 3.5 SDK.. or at
the very least has been named something else...
> > 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.
Thanks for the honest answer.. you made me chuckle. :)
Actually, I think what I'm going to do is use EvtGetEvent's timeout feature
to implement this.. I'm really only using the function in one place, so if I
isolate the event loop for the one point that function is needed, it will
work just fine.. and be reasonably elegant.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
