See the screen shot below.
If I stop legacy debug during execution with a breakpoint and make changes to the code and then resume execution, data assigned to variables gets thrown off. In the example shown, the "If" line has "Turn < 3" and hovering over "Turn" shows that it is "3", but as you can see, Debug has advanced to the line below If anyway.
Another example is that I made changes to a variable right before calling a Sub. The variable had the right value in the calling sub but was different in the called sub.
Edit:
I was just trying it with #4 beta and added a blank line above where the highlighted Debug line was and Debug single-step went to where the lines used to be. For example, if I put a blank line before:
1: For i = 1 to 20
2: x(i) = i
3: Next
where the Debug line is going from 1 to 2 to 3 and back to 1, then it becomes
1: [blank]
2: For i = 1 to 2, etc.
but the Debug line keeps going from 1 to 2 to 3 and back to 1 (which is now blank.
Again, this is "legacy debug". (Maybe we aren't supposed to be changing code in legacy debug?)
If I stop legacy debug during execution with a breakpoint and make changes to the code and then resume execution, data assigned to variables gets thrown off. In the example shown, the "If" line has "Turn < 3" and hovering over "Turn" shows that it is "3", but as you can see, Debug has advanced to the line below If anyway.
Another example is that I made changes to a variable right before calling a Sub. The variable had the right value in the calling sub but was different in the called sub.
Edit:
I was just trying it with #4 beta and added a blank line above where the highlighted Debug line was and Debug single-step went to where the lines used to be. For example, if I put a blank line before:
1: For i = 1 to 20
2: x(i) = i
3: Next
where the Debug line is going from 1 to 2 to 3 and back to 1, then it becomes
1: [blank]
2: For i = 1 to 2, etc.
but the Debug line keeps going from 1 to 2 to 3 and back to 1 (which is now blank.
Again, this is "legacy debug". (Maybe we aren't supposed to be changing code in legacy debug?)
Attachments
Last edited:
