Bill Heidler wrote:
Matt Graham's response:Are you sure this is what happens? Are the records really _that_ large that this is causing a performance problem worse than the added complexity of what your workarounds?
Can't you just resize the existing record to the new size that you want instead of messing with MemHandleNew() and DmAttachRecord()?
Bill Heidler's response:
Yes I can, but if the records are large then I have two buffers allocated
at the same time, reducing the memory space available.
Is it possible that you're not using the funcions right?I may end up doing this, but I would like to know what DmResizeRecord() is doing in terms of locking buffers, and whether there is a workaround to the POSE memory leak detection for attached buffers. I would think that anyone who used DmResizeRecord() and DmAttachRecord() would want to know the answers to these questions.
Also you might try using DmHandleNew() instead of MemHandleNew().
matt
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
