Ton van Overbeek wrote:
> Is the unallocated chunk error on the field pointer or the field
> text pointer? You could check with MemHandleSize() if the text
> field is still allocated. It will return a size of 0 if it is
> not.
I added this pre-condition in the handling of the fldChangedEvent:
if ( MemHandleSize( FldGetTextHandle( event->data.fldChanged.pField ) ) == 0 )
return true;
but I still get "Auriga (1.03a FR) just read from memory location
0x00004E32, which is in an unallocated chunk of memory.
I think calling just any Fld* API produces the error.
Luc Le Blanc
On 2006-09-19, Luc Le Blanc <[EMAIL PROTECTED]> wrote:
> When the PalmOs built-in keyboard is launched from within my app and the
> Launcher button is tapped, my app gets a fldChangedEvent for the
> currently edited field (even if no change was made) but if I try to call
> a field API on the pField passed in the event, I get an unallocated
> chunk error. How can I tell the app is closing and I must ignore such false
> events? Both the form pointer and the field pointer are valid, although
> the field text pointer is now invalid, but how can I tell without asking
> the field, an thus causing the error?
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
