At 5:58 PM -0600 1/27/03, Jeff Wheeler wrote:
In my example, DataUser can't (currently) pre-allocate the buffer because it
doesn't know how much will be needed. There are alternatives, of course. A
few of the top of my head:
- First ask how much space is needed, then pre-allocate that much in
DataUser. - Use a temporary database record has the intermediary.
That, or a Feature Pointer, or something along those lines, perhaps. You might also be able to do something using the Exchange Manager (but I'm not sure how appropriate that is for two-way communication).

Anyway, thanks for illuminating the issues.  It always helps to know what to
expect (or anticipate) in the future!
Please note that I've phrased my response with intentionally vague terms. I don't know how things will work in the future for sure. For instance, it may be possible to support "legacy" applications in a compatible way, perhaps by loading all old 68K apps into their own heap/address space. Also, special consideration may be given to the special case of sub-launching applications with SysAppLaunch (which is different from the SysUIAppSwitch context I'd been assuming).

-- Keith Rollin
-- Palm OS Emulator engineer


--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/


Reply via email to