Chris May

I thought last night was going to be a quick final build of the programs, and then I would spend most time double checking that the installs all worked, but it turned out to be a night of debugging hell. All kinds of errors when trying to run some builds on my Palm OS 3 device or emulator. But I only get these errors when I change something in the form editor, nothing in my code. Nothing in my code references anything that would cause these errors, meaning... if all you are doing is asking for the .display of an object, and setting the .display, then it doesn't really matter if that object is a textbox or a label, but for some reason, when I get to some magical limit, if I change another label to a textbox then all goes to hell.

This is all really stemming from the grid bug that I am again going to try to get an answer on.

I posted on the CASL Board 3 times (or more) about this grid bug, posts here, here, and here.

I can't believe that this isn't a "big" issue for CASL developers, so I guess that means that either 1) no one is testing their apps on Palm OS3 devices, or they are testing their apps without long enough strings to see the problem, or 2) There is something about my setup that is causing this problem, or 3) When people get this problem, they do what I did, which is to replace the labels with a textbox, but this is not a good option because the textboxes will wrap, even if its only 1 line, and I can't even run my program after switching to textboxes now for some reason that I have no way of knowing.

I uploaded another image of the bug to go along with my existing images here, here, and here, where the last of the 3 is running on OS4, so it looks fine, while the first 2 are on OS3.

I'm even posting up a sample project to cause this error, to see if I can get ANYONE to recreate the problem.