> memErrChunkLocked?!? No, it isn't!
DmResizeRecord calls MemHandleResize, which requires that the chunk not be
locked. The most probably explanation is the simplest one: the chunk is
indeed locked. For debugging purposes, try inserting a call to
MemHandleLockCount before the resize. I'll be it'll say it's not zero.
Your next step is to figure out how the chunk is getting locked (but not
unlocked). Are you using a field to edit the record in place? Fields keep
the chunk containing the text locked most of the time.
If worst comes to worst, try using PalmDebugger to set a breakpoint on
MemHandleLock. You'll see lots of calls to this trap. You only care about
the chunk that later gets resized. If you use a fresh Poser session each
time, you can predict where this chunk will be in memory - the same place it
was last time.
Just some ideas...
-
Danny
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
