The Queue of Events - Revision history

Andrea: /* Processing Events */

2017-07-06T10:39:12Z

‎Processing Events

2017-06-22T11:24:28Z

‎Processing Events

2017-06-22T11:15:24Z

2017-06-22T11:02:35Z

‎Structure of an Event

2017-06-21T17:12:23Z

‎Processing Events

2017-06-21T16:59:00Z

‎Processing Events

2017-06-21T16:57:37Z

‎Processing Events

2017-06-21T16:45:36Z

‎Processing Events

2017-06-21T16:07:47Z

2017-06-21T15:35:54Z

‎Structure of an Event

@@ Line 29: / Line 29: @@
 takes care of fetch, process and/or dispatch incoming events, the following code is an example of a minimal one.
-<syntaxhighlight lang="pawn" line>
+<syntaxhighlight lang="pawn">
 /***************************************************************
+*

@@ Line 86: / Line 86: @@
 			case SevEmergExit:
+			{
 				break;
+			}

@@ Line 114: / Line 114: @@
 	// program end
+}
 </syntaxhighlight>

@@ Line 11: / Line 11: @@
 where:
-* <code>.opcode</code> is used to uniquely identify the event
+* <code>.opcode</code> is used to uniquely identify the event type
 * <code>.p0, .p1, .p2, .p3</code> contains informations specific to that event

@@ Line 113: / Line 113: @@
+	}
 	// program end
+}
 </syntaxhighlight>

@@ Line 26: / Line 26: @@
 = Processing Events =
-In [https://en.wikipedia.org/wiki/Event-driven_programming Event-driven programming] the readmain loop of a program
+In [https://en.wikipedia.org/wiki/Event-driven_programming Event-driven programming] the main loop of a program
 takes care of fetch, process and/or dispatch incoming events, the following code is an example of a minimal one.
@@ Line 82: / Line 82: @@
 		switch( ev.opcode )
+		{
-			// script stop command
+			// <script stop> command from console
 			//
 			case SevEmergExit:
@@ Line 89: / Line 89: @@
+			}
-			// push button
+			// push button activate
 			//
 			case SevDinActive:
+			{
+				if( ev.p0 == 0 )
+			}
+		}

← Older revision		Revision as of 16:45, 21 June 2017
Line 25:		Line 25:

	= Processing Events =		= Processing Events =
		+
		+	In [https://en.wikipedia.org/wiki/Event-driven_programming Event-driven programming] the readmain loop of a program
		+	takes care of fetch, process and/or dispatch incoming events, the following code is an example of a minimal one.
		+
		+	<syntaxhighlight lang="pawn" line>
		+	/***************************************************************
		+	*
		+	* Minimal Event Processing Loop
		+	*
		+	* program.p
		+	*
		+	***************************************************************/
		+
		+	// include the library for H6105-D
		+	//
		+	#include <hydlib_cp>
		+
		+	// main function
		+	//
		+	main()
		+	{
		+	// clear display
		+	//
		+	dClear();
		+
		+	// select system font
		+	//
		+	dFont( system5x7 );
		+
		+	// place cursor
		+	//
		+	dCursor( 0, 0 );
		+
		+	// print on display
		+	//
		+	dPrintf("Processing Events");
		+
		+	// declare an event container
		+	//
		+	new BASE_EVENT(ev);
		+
		+	// enable system events
		+	//
		+	SysEvEnable();
		+
		+	// main loop
		+	//
		+	for( ;; )
		+	{
		+	// get new event from queue
		+	//
		+	EventGet( ev );
		+
		+	// process some events
		+	//
		+	switch( ev.opcode )
		+	{
		+	// script stop command
		+	//
		+	case SevEmergExit:
		+	{
		+	break;
		+	}
		+
		+	// push button
		+	//
		+	case SevDinActive:
		+	{
		+
		+	}
		+	}
		+	}
		+
		+
		+	// program end
		+	}
		+	</syntaxhighlight>

← Older revision		Revision as of 16:07, 21 June 2017
Line 16:		Line 16:
	= Events' Library Functions =		= Events' Library Functions =

		+	The library functions for events management are:

		+	* <code>#define BASE_EVENT(%1) Event:%1[.opcode, .p0, .p1, .p2, .p3]</code> is a macro to help in creating an event container
		+	* <code>SysEvEnable()</code> enable the system to post events into the queue
		+	* <code>SysEvDisable()</code> disable the system to post events into the queue
		+	* <code>EventGet( BASE_EVENT(ev) )</code> get an event from the queue, if an event is not available will wait for
		+	* <code>EventSend( BASE_EVENT(ev) )</code> send an event to the queue, can be used to inject custom and/or simulated events

	= Processing Events =		= Processing Events =

@@ Line 5: / Line 5: @@
 = Structure of an Event =
-An event is defined in the library as an array of values <code>[.opcode, .p0, .p1, .p2, .p3]</code>
+An event is defined in the library as an array of values:
-where the first value <code>.opcode</code> is used to identify the event and the  subsequent values <code>.p0, .p1, .p2, .p3</code> contains informations specific to that event.
 = Events' Library Functions =