"Bradly J. Barton" <[EMAIL PROTECTED]> wrote in message
news:45967@palm-dev-forum...
>
> Ok.. I was incorrect.. this function is not supported on pre-3.5
devices. If
> it is compiled with the 3.1 SDK and uses this function, it works on
Post-3.5
> devices.. but if you compile it under the 3.5 SDK, it breaks on
pre-3.5
> devices. (I didn't know this until just now because I'm only just now
> migrating a couple of projects to the 3.5 SDK and hadn't tested it on
a pre
> 3.5 ROM).
>
> Why on Earth would Palm break functioning code like this??
If you look at the EvtSetNullEventTick definition in the 3.5 SDK, you'll
see that it uses the trap sysTrapEvtSetNullEventTick. Looking in
CoreTraps.h for this, you get the lines:
// Ask for a null event sooner (replaces a macro which Poser hated)
sysTrapEvtSetNullEventTick,
So, it looks like in the 3.1 SDK, this was a macro, but it got replaced
by a real PalmOS 3.5+ trap. The call is documented in the 3.5 SDK docs
as being a macro on older OS versions. This change should also have
been documented in the compatability guide, but it seems to have been
missed.
--
Ben Combee, [EMAIL PROTECTED]
Techwood Broadcasting Foundation, Austin Bureau
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
