Component Debugger - Revision history

DavidA at 08:37, 2 July 2019

2019-07-02T08:37:35Z

BenR at 16:49, 7 March 2014

2014-03-07T16:49:16Z

JonnyW: XML import

2014-01-16T15:58:50Z

XML import

ReeceL at 14:31, 23 September 2013

2013-09-23T14:31:26Z

ReeceL at 14:37, 20 September 2013

2013-09-20T14:37:44Z

ReeceL at 14:33, 20 September 2013

2013-09-20T14:33:39Z

ReeceL at 14:32, 20 September 2013

2013-09-20T14:32:36Z

ReeceL at 14:30, 20 September 2013

2013-09-20T14:30:14Z

ReeceL at 14:10, 22 August 2013

2013-08-22T14:10:05Z

ReeceL at 07:54, 22 August 2013

2013-08-22T07:54:32Z

← Older revision		Revision as of 08:37, 2 July 2019
Line 1:		Line 1:
−	~~<sidebar>Sidebar: Flowcode Help Overview:ToolsViews</sidebar>~~
	The '''Component Debugger''' is used for tracking, monitoring and developing components, it displays [[API Overview\|API functions]] such as timers, events, macro calls such as [[Component Macro Icon Properties\|Component Macros]] and [[Simulation Macro Icon Properties\|Simulation Macros]] and much more. It can easily track button presses, switch triggers, as well as component properties and the function process.		The '''Component Debugger''' is used for tracking, monitoring and developing components, it displays [[API Overview\|API functions]] such as timers, events, macro calls such as [[Component Macro Icon Properties\|Component Macros]] and [[Simulation Macro Icon Properties\|Simulation Macros]] and much more. It can easily track button presses, switch triggers, as well as component properties and the function process.

← Older revision		Revision as of 16:49, 7 March 2014
Line 1:		Line 1:
−	<sidebar>Sidebar: Overview ~~of Simulation~~</sidebar>	+	<sidebar>Sidebar: Flowcode Help Overview:ToolsViews</sidebar>
	The '''Component Debugger''' is used for tracking, monitoring and developing components, it displays [[API Overview\|API functions]] such as timers, events, macro calls such as [[Component Macro Icon Properties\|Component Macros]] and [[Simulation Macro Icon Properties\|Simulation Macros]] and much more. It can easily track button presses, switch triggers, as well as component properties and the function process.		The '''Component Debugger''' is used for tracking, monitoring and developing components, it displays [[API Overview\|API functions]] such as timers, events, macro calls such as [[Component Macro Icon Properties\|Component Macros]] and [[Simulation Macro Icon Properties\|Simulation Macros]] and much more. It can easily track button presses, switch triggers, as well as component properties and the function process.

← Older revision		Revision as of 15:58, 16 January 2014
Line 15:		Line 15:

	See the [[API Debug]] section for further technical information, including an example of the functions in use, you can download the Flowcode file by clicking on the file name on the following link:		See the [[API Debug]] section for further technical information, including an example of the functions in use, you can download the Flowcode file by clicking on the file name on the following link:
−	:~~[[File:~~SIMAPI_Debug_Print.fcfx]]	+	:{{Fcfile\|SIMAPI_Debug_Print.fcfx\|SIMAPI_Debug_Print}}

@@ Line 7: / Line 7: @@
 [[File:Gen_Component_Debugger_01.png|center]]
-The Component Debugger also offers various useful options to extend the information you can gather and test, from a detailed component tree in the property pane to showing hidden objects, mouse position and the position of the objects on the panel to identify and issues in the graphics and simulation and find areas to improve upon with the help of this additional information.
+The Component Debugger also offers various useful options to extend the information you can gather to test a component. Information such as a detailed component tree shown in the [[Properties Panel]] as well as mouse position, object position and the ability to show hidden objects on the Dashboard Panel and System Panel can be used to identify any graphical, simulation and functionality issues to find areas to improve upon with the help of this additional information.
 The position of components and objects are very useful to see in simulation, it allows you to accurately test accurate movement and animation as well as collision detection and input devices such as switches, buttons and dials etc.

← Older revision		Revision as of 14:37, 20 September 2013
Line 15:		Line 15:

	See the [[API Debug]] section for further technical information, including an example of the functions in use, you can download the Flowcode file by clicking on the file name on the following link:		See the [[API Debug]] section for further technical information, including an example of the functions in use, you can download the Flowcode file by clicking on the file name on the following link:
−	:[[SIMAPI_Debug_Print.fcfx]]	+	:[[File:SIMAPI_Debug_Print.fcfx]]

← Older revision		Revision as of 14:33, 20 September 2013
Line 14:		Line 14:
	There are simulation functions available to print text onto the 'Component Debugger' to diagnose and identify errors by allowing a trace to be printed during events, this ensures that the program is running correctly and that the flowchart logic is sound.		There are simulation functions available to print text onto the 'Component Debugger' to diagnose and identify errors by allowing a trace to be printed during events, this ensures that the program is running correctly and that the flowchart logic is sound.

−	See the [[API Debug]] section for further technical information, including an example of the functions in use, you can download the Flowcode file by clicking on the file name on the following link: [[SIMAPI_Debug_Print.fcfx]].	+	See the [[API Debug]] section for further technical information, including an example of the functions in use, you can download the Flowcode file by clicking on the file name on the following link:
		+	:[[SIMAPI_Debug_Print.fcfx]]

← Older revision		Revision as of 14:32, 20 September 2013
Line 13:		Line 13:

	There are simulation functions available to print text onto the 'Component Debugger' to diagnose and identify errors by allowing a trace to be printed during events, this ensures that the program is running correctly and that the flowchart logic is sound.		There are simulation functions available to print text onto the 'Component Debugger' to diagnose and identify errors by allowing a trace to be printed during events, this ensures that the program is running correctly and that the flowchart logic is sound.
		+
		+	See the [[API Debug]] section for further technical information, including an example of the functions in use, you can download the Flowcode file by clicking on the file name on the following link: [[SIMAPI_Debug_Print.fcfx]].

← Older revision		Revision as of 14:30, 20 September 2013
Line 10:		Line 10:

	The position of components and objects are very useful to see in simulation, it allows you to accurately test accurate movement and animation as well as collision detection and input devices such as switches, buttons and dials etc.		The position of components and objects are very useful to see in simulation, it allows you to accurately test accurate movement and animation as well as collision detection and input devices such as switches, buttons and dials etc.
		+
		+
		+	There are simulation functions available to print text onto the 'Component Debugger' to diagnose and identify errors by allowing a trace to be printed during events, this ensures that the program is running correctly and that the flowchart logic is sound.

← Older revision		Revision as of 14:10, 22 August 2013
Line 1:		Line 1:
	<sidebar>Sidebar: Overview of Simulation</sidebar>		<sidebar>Sidebar: Overview of Simulation</sidebar>
−	The '''Component Debugger''' is used for tracking, monitoring and developing components, it displays API functions such as timers, events, macro calls such as [[Component Macro Icon Properties\|Component Macros]] and [[Simulation Macro Icon Properties\|Simulation Macros]] and much more. It can easily track button presses, switch triggers, as well as component properties and the function process.	+	The '''Component Debugger''' is used for tracking, monitoring and developing components, it displays [[API Overview\|API functions]] such as timers, events, macro calls such as [[Component Macro Icon Properties\|Component Macros]] and [[Simulation Macro Icon Properties\|Simulation Macros]] and much more. It can easily track button presses, switch triggers, as well as component properties and the function process.