With MemHandleLock, once it's locked, if you lock it again it doesn't take too much time, it basically just increments the lock count. Therefore, you do not have to make dramatic change to your code, just lock it once before you call a stack of functions, and unlock it when it's done.
LionScribe,
I don't think you'll see any performance difference in either case. MemHandleLock pretty much works the same way regardless of whether or not the handle is already locked: it acquires a mutex, does some sanity checking, increments the count, and releases the mutex. The only difference comes in when the lock count is incremented to 15, at which time the OS will display the "chunk over locked" error message.
-- Keith Rollin -- Development Tools engineer
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
