Try passing flag to create separate stack while doing sysapplaunch. I faced the same problem while handling notification event and passing the flag in sysapplaunch fixed it. --- Jeff Ondich <[EMAIL PROTECTED]> wrote:
> Thanks very much for the suggestions. I have not > had trouble with empty > strings in FrmCustomAlert, and in fact, putting > non-empty strings in > those parameters has not fixed my problem. As it > happens, I have > developed a workaround for the moment, but I would > still like to know > why this function is failing in my situation. > > Thanks a lot, > > Jeff > > > P. Douglas Reeder, aka Skapti wrote: > > John Sutton wrote: > > > >> Jeff > >> I'm not sure if I'm dreaming this, but I think I > once had a problem with > >> empty strings. > >> FWIW try putting something inside the two empty > strings just to rule out > >> my paranoia. > >> ie. FrmCustomAlert( MessageAlert, "whatever", > "should be empty", "should > >> also be empty" ); > >> > > > > > > FWIW, the API docs for FrmCustomAlert say: > > > > If the variables ^1, ^2, and ^3 occur in the > message string, do not pass > > |NULL| for the arguments |s1|, |s2|, and |s3|. If > you want an argument > > to be ignored, pass the empty string (|""|). In > Palm OS 2.0 or below, > > pass a string containing a space (|" "|) instead > of the empty string. > > > > > > ... so, this is not supposed to be a problem with > OS 3 and later. > > > > > > -- > For information on using the PalmSource Developer > Forums, or to unsubscribe, please see > http://www.palmos.com/dev/support/forums/ > -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
