What the line cursor called code#

The cursor indicates that the column can be resized horizontally. The cursor indicates that a context-menu is available. The cursor indicates that a cell (or set of cells) may be selected. The cursor indicates that something can be scrolled in any direction. The cursor indicates an alias of something is to be created. Place the cursor above the cell to see the effect. Internet Explorer) does not show exactly the same cursor for the same codes. Also, you should be aware that not all browsers (i.e. Several of them look alike, so it isn't all the created cursors it makes sense to use. Right-click and select Jump To Cursor from the context menu.These are the standard cursors currently available for HTML. Stops the execution and jumps to the line where the caret is. For this purpose, you can use the Run menu commands, or the icons on the stepping toolbar of in the Debug tool window.Įach stepping action advances the execution point to the next execution location, depending on the action you choose. When a breakpoint is reached or your program is suspended, the Debug tool window becomes active and enables you to get control over the program's execution. If there are breakpoints in the called methods, they are ignored.įrom the main menu, select Run | Force Step Over or press Alt+Shift+F8.

What the line cursor called code#

Steps over the current line of code and takes you to the next line even if the highlighted line has method calls in it. All breakpoints on the way are ignored.įrom the main menu, select Run | Debugging Actions | Force Run to Cursor or press Ctrl+Alt+F9. Steps in the method even if this method is skipped by the regular Step Into.Ĭlick the Force step into button or press Alt+Shift+F7.Ĭontinues the execution until the position of the caret is reached. To skip any breakpoints on the way, use Force run to cursor. You can configure whether you want Run to Cursor to work on clicking a line number in Settings/Preferences | Build, Execution, Deployment | Debugger. Place the caret at the line where you want the program to pause.Ĭlick the Run to Cursor button or press Alt+F9.Īlso, you can Run to Cursor by clicking the line number in the gutter. Steps out of the current method and takes you to the caller method.Ĭlick the Step Out button or press Shift+F8.Ĭontinues the execution until the position of the caret is reached. If you do not want to use it automatically, go to Settings/Preferences | Build, Execution, Deployment | Debugger | Stepping and clear the Always do smart step into checkbox. You can also select it using the arrow keys or tabs and press Enter/ F7.īy default, smart step into is used every time when there are multiple method calls in the line. This feature allows you to select the method call you are interested in.įrom the main menu, select Run | Debugging Actions | Smart Step Into or press Shift+F7.Ĭlick the method. Smart step into is helpful when there are several method calls on a line, and you want to be specific about which method to enter. When debugging, you might want to concentrate on your own code and prevent debugger from stepping into library classes.Ĭlick the Step Into My Code button ( Alt+Shift+F7). To suppress stepping into some specific scripts, select the Do not step into scripts checkbox and create a list of such scripts using the toolbar buttons. To skip all library scripts, select the Do not step into library scripts checkbox. In the Settings/Preferences dialog ( Ctrl+Alt+S), go to Build, Execution, Deployment | Debugger | Stepping.

This list can be fine-tuned on the Build, Execution, Deployment | Debugger | Stepping page of the Settings/Preferences dialog ( Ctrl+Alt+S). Some scripts are skipped by Step into as you normally might not need to debug them. This feature is called Smart step into.īy default, smart step into is used every time when there are multiple method calls on the line. If there are several method calls on the line, P圜harm asks you which method to enter. Use this option when you are not sure the method is returning a correct result. Steps into the method to show what happens inside it. To skip any breakpoints on the way, use Force step over. If there are breakpoints inside the skipped methods, the debugger will stop at them. The implementation of the methods is skipped, and you move straight to the next line of the caller method. The stepping buttons are located on the Debug window toolbar. P圜harm provides a set of stepping actions, which are used depending on your strategy (for example, whether you need to go directly to the next line or enter the methods invoked on your way there). Stepping is the process of controlling step-by-step execution of the program.