Currently, the API specifies that whenever a storage handle gets resized, like through
a DmResizeRecord, or a MemHandleResize, the handle might get relocated into a
different data heap.
However, since OS 3.0, there has only been one data heap, so that storage handles will
not get moved when resized. The latest doc makes an offhand reference to this in the
description of MemHandleResize.
Can we count on this behavior in the future? In other words, will DmResizeRecord
ALWAYS return the same handle in future OS's?
It would be a huge advantage if we could count on non-moving data handles. One thing
we could do with it is make multiple indexes into a database when an application
starts up, and be able to count on the handles not changing while the application is
running.
Any comment from Palm?
Shannon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hands High Software
Award winning software for the Palm(tm) Computing platform
<http://www.handshigh.com/>
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
