🚀 go-pugleaf

Ben Combee <combee@techwood.org> wrote in message news:<MPG.18f80ae59c2a15ce989a89@news.earthlink.net>...
> > As I work my way through my program using the version 4 ROM, I keep
> > running into similar gotchas. So far, I have been able to solve most
> > of them. Here's one that's got me stumped. My form has a menu, and
> > when you click on one of the menu items, the form calls a function,
> > which retrives a bunch of numbers from a database and displays them in
> > a spreadsheet. If I go directly from my main form to the form in
> > question (i.e., form A to from C), everything works find. However, if
> > I go the form in question indirectly (i.e., form A to form B to form
> > C), the called function (the same code in each case) barfs on this
> > line: "FrmCopyTitle(pFrm, "loading . . .");" As I said, this exact
> > same patch of code works fine when it is reached by a more direct
> > route. When I take the indirect route, I get this error message:
> 
> FrmCopyTitle requires that the original title defined in the form be at 
> least as long as the string to which you're setting the title.  So, if 
> the title on the form as defined in Constructor or PilRC isn't at least 
> 13 characters, that FrmCopyTitle call may overwrite unallocated memory.
> 
> The Palm OS 4 debug ROMs have a lot more debugging checks in them than 
> previous ROM.

I don't think the title length is the problem. The new title is 

"loading . . .". 

The title it replaces is 

"Chi Square Sample Size"


As I noted before, the function handles this title change OK when the
form is reached by the shorter route but not when it is reached by the
longer route. That's why I wondered whether the error message might
have been triggered by a stack overflow.