> I have coded a MinMemoryCheck routine to place at the beginning of
PilotMain
> startup and various process intensive functions. How can I determine what
> the minimum available should be to allow the program to startup?
I've used pre-flighting, both in the dynamic heap and in the storage heap,
but I don't recommend it. The problem is that other applications can
allocate memory any time you go around the event loop, and hacks can
allocate memory any time you call a Palm OS API (systrap). Better to treat
allocation failures as user errors rather than system errors. This can
require a lot of rollback code, depending on what you're trying to do. To
test this, you should use Gremlins in combination with an application that
almost fills the dynamic and/or storage heaps.
--
Danny @ Palm
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
