Re: Debugger Testing
On Monday, July 7, 2003, at 03:37 PM, Edwin Gore wrote: Okay... I'm beginning to feel like maybe I'm going crazy, since I can't believe other people would not be inconvenienced by step-over in the 2.01 debugger not working. Therefore, I have devised a test - if you download http://www.shinra.com/debugtest.rev and run it you will see a stack with a single button on it. Turn on the debugger, and click the button. The debugger will open, and if you click on on the Step Over button in the debugger, you should remain in the script for the button, click "step Over" a few times, and then the name of the button should change. What I am getting instead, on all of my machines, even after uninstalling and reinstalling, is that I click step over, and when it gets to the function, it steps into it. I KNOW that step over was working before - I just don't know if it was in the beta, or in 2.0. If a couple of people could try this stack to verify that it's a problem for them, I would really appreciate it. Also, if anyone still has a copy of the installer for the pre-release 2.0, I would appreciate the opportunity to experiment with it as well... I NEED to be able to debug... Thanks, Edwin Gore We already reported this bug to them. It was verified. I bet it will get fixed in the next release. Best regards, Mark Talluto http://www.canelasoftware.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Debugger Testing
You aren't going crazy Edwin, it happens here too, though it's inconsistent. I seem to recall I've seen this mentioned several times in the lists by others. I don't know if anybody has formally reported this as a bug though. Last time I tried to look something up in bugzilla it gave me an error (though it had worked for me previously). I find it fairly infuriating myself, but how much of a problem this to you personally will of course depend on the structure of your scripts. I just try and work around it as far as possible by judicious placement of breakpoints and use of the Run button, or sometimes putting a breakpoint inside a conditional as in : if myVar = 300 then breakpoint end if can cut out the need to step through the preceding 299 iterations of a function call :-) martin baxter >From: Edwin Gore >Okay... > >I'm beginning to feel like maybe I'm going crazy, since I can't believe >other people would not be inconvenienced by step-over in the 2.01 debugger >not working. ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Debugger Testing
Okay... I'm beginning to feel like maybe I'm going crazy, since I can't believe other people would not be inconvenienced by step-over in the 2.01 debugger not working. Therefore, I have devised a test - if you download http://www.shinra.com/debugtest.rev and run it you will see a stack with a single button on it. Turn on the debugger, and click the button. The debugger will open, and if you click on on the Step Over button in the debugger, you should remain in the script for the button, click "step Over" a few times, and then the name of the button should change. What I am getting instead, on all of my machines, even after uninstalling and reinstalling, is that I click step over, and when it gets to the function, it steps into it. I KNOW that step over was working before - I just don't know if it was in the beta, or in 2.0. If a couple of people could try this stack to verify that it's a problem for them, I would really appreciate it. Also, if anyone still has a copy of the installer for the pre-release 2.0, I would appreciate the opportunity to experiment with it as well... I NEED to be able to debug... Thanks, Edwin Gore ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
