Simulation Events - Revision history

BenR at 15:26, 16 January 2023

2023-01-16T15:26:41Z

BenR at 15:26, 16 January 2023

2023-01-16T15:26:09Z

BenR at 12:13, 16 January 2023

2023-01-16T12:13:47Z

BenR at 12:13, 16 January 2023

2023-01-16T12:13:29Z

DavidA at 08:38, 2 July 2019

2019-07-02T08:38:47Z

BenR at 17:08, 7 March 2014

2014-03-07T17:08:48Z

Admin at 09:15, 24 January 2014

2014-01-24T09:15:31Z

ReeceL: /* Video instructions */

2013-09-04T16:01:29Z

Video instructions

ReeceL at 12:55, 2 September 2013

2013-09-02T12:55:44Z

ReeceL at 15:25, 30 August 2013

2013-08-30T15:25:46Z

← Older revision		Revision as of 15:26, 16 January 2023
Line 8:		Line 8:


−	The events tab is hidden by default but can be included by using the [[Global_Settings\|Global Options - ~~Tree~~ tab]].	+	The events tab is hidden by default but can be included by using the [[Global_Settings\|Global Options - UI Trees tab]].

← Older revision		Revision as of 15:26, 16 January 2023
Line 6:		Line 6:
	===Event Management===		===Event Management===
	The [[Project Explorer]] events tab is used to list all the available events and provides a quick way of seeing which events are active in your Flowcode project.		The [[Project Explorer]] events tab is used to list all the available events and provides a quick way of seeing which events are active in your Flowcode project.
		+
		+
		+	The events tab is hidden by default but can be included by using the [[Global_Settings\|Global Options - Tree tab]].

← Older revision		Revision as of 12:13, 16 January 2023
Line 18:		Line 18:
	The [[Component Debugger]] window has a option to log events as they are fired which is useful for debugging purposes.		The [[Component Debugger]] window has a option to log events as they are fired which is useful for debugging purposes.

−	Full details surrounding each of the events in Flowcode can be found here [[Simulation_Functionality#Events]].	+	Full details surrounding each of the events in Flowcode can be found here [[Simulation_Functionality#Events\|Simulation Library]].

← Older revision		Revision as of 12:13, 16 January 2023
Line 18:		Line 18:
	The [[Component Debugger]] window has a option to log events as they are fired which is useful for debugging purposes.		The [[Component Debugger]] window has a option to log events as they are fired which is useful for debugging purposes.

−	Full details surrounding each of the events in Flowcode can be found here [[~~Event_Reference~~]].	+	Full details surrounding each of the events in Flowcode can be found here [[Simulation_Functionality#Events]].

← Older revision		Revision as of 08:38, 2 July 2019
Line 1:		Line 1:
−	~~<sidebar>Sidebar: Flowcode Help Overview:Simulation</sidebar>~~
	[[File:ProjectExplorerEventsTab.jpg\|right]]		[[File:ProjectExplorerEventsTab.jpg\|right]]
	A Flowcode simulation event is similar to an [[Interrupt Icon Properties\|Interrupt]] but aimed at performing a specific job. The events will not be referenced at all for downloaded microcontroller code but may be used in the generation of such code.		A Flowcode simulation event is similar to an [[Interrupt Icon Properties\|Interrupt]] but aimed at performing a specific job. The events will not be referenced at all for downloaded microcontroller code but may be used in the generation of such code.

@@ Line 1: / Line 1: @@
-<sidebar>Sidebar: What Is a Macro?</sidebar>
+<sidebar>Sidebar: Flowcode Help Overview:Simulation</sidebar>
 [[File:ProjectExplorerEventsTab.jpg|right]]
 A Flowcode simulation event is similar to an [[Interrupt Icon Properties|Interrupt]] but aimed at performing a specific job. The events will not be referenced at all for downloaded microcontroller code but may be used in the generation of such code.

← Older revision		Revision as of 09:15, 24 January 2014
Line 18:		Line 18:

	The [[Component Debugger]] window has a option to log events as they are fired which is useful for debugging purposes.		The [[Component Debugger]] window has a option to log events as they are fired which is useful for debugging purposes.
		+
		+	Full details surrounding each of the events in Flowcode can be found here [[Event_Reference]].

@@ Line 21: / Line 21: @@
 ===Video instructions===
-See the [http://www.youtube.com/watch?v=DflA2gULQuw&list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ&index=26 Simulation Events] video for a overview of the simulation events and demonstrates the [[Event Mouse.Click|Mouse.Click]] event by creating the macro Ev_Click event macro and using a [[Simulation Macro Icon Properties|Simulation Macro]] to change the colour of an object.
+The [http://www.youtube.com/watch?v=DflA2gULQuw&list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ&index=26 Simulation Events] video consists of an overview of the simulation events and a demonstration of the [[Event Mouse.Click|Mouse.Click]] event by creating the macro Ev_Click event macro and using a [[Simulation Macro Icon Properties|Simulation Macro]] to change the colour of an object.
 <div align="center">
 {{#ev:youtube|DflA2gULQuw|640}}
 </div>

@@ Line 1: / Line 1: @@
 <sidebar>Sidebar:What Is a Macro?</sidebar>
 [[File:ProjectExplorerEventsTab.jpg|right]]
-A Flowcode simulation event is similar to an [[Interrupt Icon Properties|Interrupt]] but aimed at performing a specific job. The events will not be referenced at all for downloaded microcontroller code but may be used in the generation of such code. Another key difference between events and interrupts is that events can occur at any time whereas interrupts can only occur whilst the simulation is running.
+A Flowcode simulation event is similar to an [[Interrupt Icon Properties|Interrupt]] but aimed at performing a specific job. The events will not be referenced at all for downloaded microcontroller code but may be used in the generation of such code.
-===Project explorer events tab===
+Another key difference between events and interrupts is that events can occur at any time whereas interrupts can only occur whilst the simulation is running.
 The [[Project Explorer]] events tab is used to list all the available events and provides a quick way of seeing which events are active in your Flowcode project.
@@ Line 15: / Line 17: @@
 Each event macro will have a return variable which may or may not be used internally by Flowcode, refer to the event description for specific details.
-The component debugger window has a option to log events as they are fired which is useful for debugging purposes.
+The [[Component Debugger]] window has a option to log events as they are fired which is useful for debugging purposes.