Dan,
>I found out that you should not pass an empty string to FrmCustomAlert.
>Try to use " " (one space) instead of "".
>
>Donno Y but it works !!! :o)
From a post by Bill Goodman back in July 1997...
At 1:59am -0500 97-07-03, Pilot Developers Forum List wrote:
>Date: 1 Jul 1997 12:14:00 -0700
>From: Bill Goodman <[EMAIL PROTECTED]>
>Subject: FrmCustomAlert bug
>
>Here's a nice obscure bug in version 1.0.6 of the OS (I have not looked to
>see if it still exists in version 2).
>
>FrmCustomAlert assumes that parameter strings passed in will have a length
>of at least 1. If they don't, it writes past the end of a block in your
>heap.
>
>For example, suppose you have an alert which says "Memory heaps are^1 OK."
>and you want to substitute either "" or " not". In the first case,
>FrmCustomAlert will write 1 byte past the end of one of its internally
>generated memory blocks.
>
>In my case, whenever I called FrmCustomAlert it had the surprising result
>of causing a bus error the NEXT time my application was launched!
I think this bug was fixed around July 1998, so that means it exists
in 1.0, 2.0, and 3.0 (not sure?) versions of the ROM. The fix would
be in the 3.1 ROMs. Note that it's only a problem if your template
string contains a ^<number> parameter that corresponds to the ""
string being passed in.
-- Ken
Ken Krugler
TransPac Software, Inc.
<http://www.transpac.com>
+1 530-470-9200
