Interesting, thanks! Does that imply that the intersegment jumps include logic to lock the destination chunk and unlock the source chunk? I was just assuming that all code sections were locked in memory while the app was executing. Did your warning pertain just to callbacks that hit after the app has closed, or do I need to be more careful with the section jumping?
Come to think of it, how would I go about locking code sections? I guess there are handles to be had from the app db? Thanks again for the swift wisdom, -Rob -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
