Debugging via code - Revision history

Jwatson at 19:32, 20 November 2012

2012-11-20T19:32:40Z

Jwatson at 19:25, 20 November 2012

2012-11-20T19:25:52Z

Jwatson at 19:23, 20 November 2012

2012-11-20T19:23:36Z

Jwatson at 18:02, 20 November 2012

2012-11-20T18:02:31Z

Jwatson at 18:01, 20 November 2012

2012-11-20T18:01:19Z

Jwatson: Created page with "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 win..."

2012-11-19T22:17:06Z

Created page with "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 win..."

New page

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.

[[File:Debugger_Windows_Example.png]]

← Older revision		Revision as of 19:32, 20 November 2012
Line 1:		Line 1:
−	<yambe:breadcrumb>General ~~Programming~~\|General Programming</yambe:breadcrumb>	+	<yambe:breadcrumb self="Debug Via Code">General\|General Programming</yambe:breadcrumb>
	<br />		<br />

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:General Programming}}
+<yambe:breadcrumb>General Programming|General Programming</yambe:breadcrumb>
-<yambe:breadcrumb self="Debugging via Code" />
 <br />

← Older revision		Revision as of 19:23, 20 November 2012
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.

@@ Line 1: / Line 1: @@
 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.
+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. <br /><br />
 [[File:Debugger_Windows_Example.png]] <br /><br />

← Older revision		Revision as of 18:01, 20 November 2012
Line 3:		Line 3:
	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.		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.

−	[[File:Debugger_Windows_Example.png]]	+	[[File:Debugger_Windows_Example.png]] <br /><br />
		+
		+	{\|
		+	!min-width="50 px"\|'''Debugger Window''' \|\| '''Pragma Statement'''
		+	\|-
		+	\|Global Variables \|\| <syntaxhighlight lang="ROBOTC">#pragma DebuggerWindows("Globals")</syntaxhighlight>
		+	\|-
		+	\|Local Variables \|\| <syntaxhighlight lang="ROBOTC">#pragma DebuggerWindows("Locals")</syntaxhighlight>
		+	\|-
		+	\|Debug Stream \|\| <syntaxhighlight lang="ROBOTC">#pragma DebuggerWindows("debugStream")</syntaxhighlight>
		+	\|-
		+	\|Joystick Control - Basic\|\| <syntaxhighlight lang="ROBOTC">#pragma DebuggerWindows("joystickSimple")</syntaxhighlight>
		+	\|-
		+
		+	\|}