I recently updated a working app from SDK 3.1 to SDK 3.5,
performing substitutions of old data types and using the
new ones where appropiate, instead of including
<PalmCompatibility.h>.
Thing is that I'm using a Palm OS 3.5 ROM transferred from
a Palm Vx --which is also our client's target platform--,
and now I experience the following behaviour:
I have a form with a table and a scrollbar, where I can
see the aggregate lines of an order, and that it doubles
itself as the table where articles to be ordered appear.
Each order line is dinamically allocated, and when order
is finished --or an old order has been edited-- we detect
changes, ask to save them, we do it, and we do a FrmGotoForm
to a form where all orders for the present client are shown...
but after the event handler for the order process receives
the last event --a WinExitEvent--... no other form receives
further events, but the event loop regurlaly polls nilEvents,
keyDownEvents, penDown/penUpEvents...
Worse, suspecting there could be a problem with having only
two segments, I segmented my app further, adding a third
segment, and now, even when each segment is less populated
and there should be less problems of lack of memory, my
MemHandleNew calls now fail...
I have extern global variable references, �could this be
an issue?
Thanks in advance.
ps. Of course, this project didn't exhibit this behaviour
when compiled and tested with the SDK 3.1...
--
Juan de Dios Santander Vela
Palm OS Developer
[EMAIL PROTECTED]
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
