That's all well and good.. and I can understand them wanting to replace it
with a real trap (the macro before made a modification to a UI Structure,
which was a flag apparently monitored by the EvtGetEvent function)... but
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.



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

Reply via email to