Difference between revisions of "Debugging via code"

From ROBOTC API Guide
Jump to: navigation, search
Line 1: Line 1:
 +
{{DISPLAYTITLE:General Programming}}
 +
<yambe:breadcrumb self="Debugging via Code" />
 +
<br />
 +
 
In ROBOTC, users may find the need to open certain debugger windows every time the program runs. Luckily, ROBOTC has a coding option that allows users to set certain debug windows to do just that: the DebuggerWindows() pragma statement.  
 
In ROBOTC, users may find the need to open certain debugger windows every time the program runs. Luckily, ROBOTC has a coding option that allows users to set certain debug windows to do just that: the DebuggerWindows() pragma statement.  
  

Revision as of 19:23, 20 November 2012

Debugging via Code


In ROBOTC, users may find the need to open certain debugger windows every time the program runs. Luckily, ROBOTC has a coding option that allows users to set certain debug windows to do just that: the DebuggerWindows() pragma statement.

To use this feature, each window that needs opened must have its own '#pragma debuggerwindow("DebugName") ' statement prior to any other code in the program (it is recommended to place them directly under the Motor and Sensors Setup pragma statements). For instance, #pragma DebuggerWindows ("Globals") is required to open the Global Variables window each time a program runs.

Debugger Windows Example.png

Debugger Window Pragma Statement
Global Variables
#pragma DebuggerWindows("Globals")
Local Variables
#pragma DebuggerWindows("Locals")
Debug Stream
#pragma DebuggerWindows("debugStream")
Joystick Control - Basic
#pragma DebuggerWindows("joystickSimple")