Sorry if this is in the manuals or update guide somewhere but I looked
and didn't find it. I also searched the news group for other articles
an didn't see one that I missed.
The following short snipit of code works great on 3.3 but not in 3.5
oldfrm = FrmGetActiveForm();
frm = FrmInitForm (EditMemoForm);
// FrmSetEventHandler (frm, EditMemoHandleEvent);
// deleted code that used to initialize the form
FrmDrawForm (frm);
do{
<break point1>
button = FrmDoDialog (frm);
<break point2>
... code to analize buttons...
The form in question has two buttons and a check box which was created
with Constructor 1.5b5. (there are not text fields - nothing else but
that). If I use a debugger, then I get to the first break point
without difficulty even with the currently remarked-out code present.
Pressing "run" or "step over" at that point will cause CW R6 (Windows
2000) to go to the "this program is running and stop is not available)
mode. I can set the check box or whatever, but pressing either of the
two push buttons will cause either
1. a "MemMgr line 4432 free ptr" error in the debug rom,
2. a "read directly from an unallocated chunk" non-debug rom.
Sometimes, the form /does/ clear of the screen and the previous form
starts getting nil events in its own form event handler (how the is
that?) but I never get to the second break point even when that happens.
Is it the "FrmDrawForm" that is evil? or the FrmDoDialog?
As I said, if I load up the 3.3 rom in the emulator (version 3.05a) then
it works great. It also works on my Vx running 3.3. But putting 3.5 on
the Vx caused it to crash here.
The romfiles are called....palmos-35-dr4-en-ez.rom
palmos-35-dr4-en-ezdbg.rom
the only thing I can think of, is that it is necessary in 3.5 to delete
the old form before I call DoDialog, but what then is the "save bits"
for?
derik
email: [EMAIL PROTECTED]
WWW: http://www.pobox.com/~derik
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
