The unusual behavior I noticed was: Form with 2 buttons. Button A opens Form A Button B opens Form B Put a break point in the open event of Form A. Press Button B (to open form B). The debugger stops in break point of Form A but opens Form B. (A doesn't call B) I wouldn't really care except that I am trying to debug an event when I open Form A. Of course, when I open Form A it does not stop at the break point in Form A. But the code acts as though it went through it. I am using CodeWarrior 7. I had originally built this project with CodeWarrior 6 and I upgraded it thinking it would be better. The original problem way back when was in one area of the application I could consitently cause a problem where it claimed I was writting to the screen directly. (I don't even know how one does that and have no interest in doing so.) Since I was using a lot of global space I decided to reduce that (and test as I went along to make sure I wasn't making more problems.). Everything was proceding somewhat normally until I got closer to my goal. I was going on the assumption that using too much global space might be overrunning stack or something else and producing a memory stomp which was leading to the writing directly to screen error. This still might be true. I may now have changed the area where the global space and this other area collide and now I am getting different behavior.(since something else is stomping on an area of memory.) I am a little light on how Palm manages memory and yes I have read the manuals. Is what I think is happening a reasonable explanation? Thanks, Jim "Steve Mann" <[EMAIL PROTECTED]> wrote in message news:44309@palm-dev-forum... > > >Could it be I have reached a state where the globals (still too large) are > >colliding with the stack or causing some sort of weirdness there? Should I > >just bravely trudge on and keep reducing my global usage? > > If you didn't have this problem before, I doubt reducing your global > space would cause the problem, unless your moving a lot of globals > into functions, thereby putting them on the stack. Stack problem > usually manifest themselves more severely than you describe. > > Personally, I think it's good to track down a problem when you first > find it (and I _always_ work that way :-)). It's not clear to me > exactly what your problem is from your description. Can you describe > it more clearly, or in more detail? > > Regards, > Steve Mann > -- > ------------------------------------------- > Creative Digital Publishing Inc. > 1315 Palm Street, San Luis Obispo, CA 93401-3117 > ------------------------------------------- > 805.784.9461 805.784.9462 (fax) > [EMAIL PROTECTED] http://www.cdpubs.com > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
