@@ -34,7 +34,7 @@ If you would relinquish control to the computer, simply press the Resume Program
Doing so without muting all breakpoints will cause the program to pause at the next breakpoint it reaches.
#### * Mute Breakpoints
By pressing this button, all breakpoints will be "muted". A muted breakpoint remains in the list of breakpoints ([described here](#breakpoints-menu)), but the program will not stop at it.
By pressing this button, all breakpoints will be "muted". A muted breakpoint remains in the list of breakpoints ([described under Breakpoints Menu](#breakpoints-menu)), but the program will not stop at it.
<palign="center">
<imgsrc="https://i.imgur.com/l480710.png"/>
...
...
@@ -57,7 +57,7 @@ A basic example for how to set a condition is shown below.
</p>
### Logging Breakpoint
A basic breakpoint has the option to log the Stack trace (or simply state that it was reached). This is similar to using a print statement, except it is much easier to guarantee its removal once it is no longer needed (using the menu [described here](#breakpoints-menu)). Additionally, it makes it much easier to work backwards, as the exact route to reach that point has been printed.
A basic breakpoint has the option to log the Stack trace (or simply state that it was reached). This is similar to using a print statement, except it is much easier to guarantee its removal once it is no longer needed (using the menu [described under Breakpoints Menu](#breakpoints-menu)). Additionally, it makes it much easier to work backwards, as the exact route to reach that point has been printed.
Setting these options can be done by left clicking the breakpoint and doing the following:
...
...
@@ -69,4 +69,14 @@ Setting these options can be done by left clicking the breakpoint and doing the
Created by setting a breakpoint on a line that declares a variable/field. This suspends the program anytime the variable declared on that line is touched. Useful for finding where the value is being set incorrectly, without having to step through large chunks of code by hand.
## Breakpoints Menu
The Breakpoint Menu can be opened by clicking the button with two red dots (the "View Breakpoints..." button) in the debug window.
The Breakpoints menu is extremely useful for modifying/finding/removing all of the created breakpoints. This menu has a list of every breakpoint that was set throughout the entire program and allows for each one to be disabled individually. By disabling, you can temporarily "remove" the breakpoint without actually removing it from the list, making it very easy to add back in later.
By double clicking a breakpoint in the list, it will take you to where that breakpoint is in the code, allowing for quick access to the code that is being analyzed.
By selecting a breakpoint in the menu, the line will be displayed within the window. This allows the line to be viewed and for the removal of the breakpoint without jumping around the code in the main window.
