Yes, I had turned off all optimizations. I also tried it with all inlining turned off. Jim "Ben Combee" <[EMAIL PROTECTED]> wrote in message news:44318@palm-dev-forum... > > "Jim Kennedy" <[EMAIL PROTECTED]> wrote in message > news:44311@palm-dev-forum... > > > > 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. > > Have you turned off all optimization for your project? Oddness with > breakpoints can often be explained by code rearrangement that the > optimizer does. Sliding the global optimization panel down to 0 > prevents this kind of rearrangement which can confuse the program flow. > > -- > Ben Combee, [EMAIL PROTECTED] > Techwood Broadcasting Foundation, Austin Bureau > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
