Hi,
my form A has a custom event which calls FldNewField(). When I trigger this
event via FrmDispatchEvent() from within the event handler of form A,
everything works fine.
Now I'm in the event handler of the modal popup form B and all I do is
"FrmReturnToForm(Form_A);
FrmDispatchEvent(That_custom_event_I_was_talking_about);".
The FldNewField() call will now eventually crash the emulator (it will
squeak about a memory read into a non-allocated chunk of memory). BUT it
works fine on a real Palm.
To make things even more complicated, it seems to matter whether I put in
some debug info - when calling some ErrDisplay() calls inbetween, the system
will actually create that new field. I can even select it. As soon as I
change one character though, the system will crash again (same error).
Unfortunately I do not have a matching Palm/POSE configuration - I'm using a
Palm V w/ OS 3.3 while POSE is set to a Palm III w/ OS 3.3. I've tried ROM
Transfer.prc but the transfered ROM does always immediately crash when fed
into POSE.
POSE is 3.0a5, Win32.
bt reports:
WinDisplayToWindowPt + $2bd12fe0
EvtGetEvent + $946a95b0
PL_EventLoop + $1405fbb0 ( <-- main event loop of my application,
obviously)
PilotMain + $a10ef2d0
I remember Mr. Flaumenhaft having a similar problem - maybe those two are
related? Or did I simply miss something very obvious?
--
Michael A. Krehan <[EMAIL PROTECTED]>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
