> Constructor is totally unusable on the box, as well. Instantly starts > popping up dialogs claiming it's out of memory. It acts almost like an > old Windows 3.0 program that has run out of GDI memory and blindly > trudged forward. (Missing GUI elements and other oddball behavior) > > Having a gig of RAM in the box wouldn't be throwing that old fossil for > a loop would it?
Yes, that's the problem. Constructor for Palm OS, hosted on Win32, has a major problem with lots of memory, and it seems to start up around the 512MB mark. PalmSource documentes this problem in the documentation that comes with Constructor 1.8 (as released with Palm OS SDK 5.0), but they don't have a solution for it yet. > At any rate, I'm debugging via POSE compiled from Handspring's sources. > Debugging directly from the handheld, which I'd prefer to do, seems not > to work under Windows 2K. Device debugging should work, but it requires using Handspring's desktop software and their USB driver. Also, the use of the DebugPrefs program from their site can be very useful, as documented at my palmoswerks article at http://www.palmoswerks.com/stories/storyReader$25. If you're using Palm's desktop software, you have to replace it with the one from Handspring's site to get a USB driver that works for debugging to these devices. > The single-step lags are most noticeable on StrCopy calls and the like. > Sometimes takes over 20 seconds to skip to the next line. On the bright > side, it gives me a chance to grab another cup of coffee. Wow! Part of this is due to how CW does stepping -- basically, when you step over a routine like this, the debugger goes through, figures out the local instructions, and inserts breakpoints at all the spots where the routine could exit. -- Ben Combee <[EMAIL PROTECTED]> CodeWarrior for Palm OS technical lead Get help at http://palmoswerks.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
