Keyboard (Chili Framework) - Revision history

Chili at 03:56, 13 October 2017

2017-10-13T03:56:30Z

2017-10-02T13:04:14Z

‎Example of Use

2017-06-27T09:26:47Z

‎Virtual Key Codes

2017-02-18T05:50:58Z

‎Event

2017-02-12T12:07:24Z

‎Example of Use

2017-02-12T11:50:17Z

2016-07-21T03:58:45Z

‎Virtual Key Codes

2016-07-15T02:38:19Z

2016-07-14T03:47:29Z

‎ReadKey vs. ReadChar

2016-07-14T03:43:26Z

‎Members

@@ Line 2: / Line 2: @@
 == Example of Use ==
-<syntaxhighlight lang="cpp" line="1" >
+<syntaxhighlight lang="cpp" line>
 // how to respond to key release event

@@ Line 6: / Line 6: @@
 // keep processing events as long as queue contains them
-while( !wnd.kbd.IsEmpty() )
+while( !wnd.kbd.KeyIsEmpty() )
+{
 	// get an event from the queue

@@ Line 85: / Line 85: @@
 * <code>VK_SPACE</code>
 * <code>VK_SHIFT</code>
-* <code>VK_ENTER</code>
+* <code>VK_RETURN</code>
 * <code>VK_ESCAPE</code>
 See the Microsoft [https://msdn.microsoft.com/en-us/library/windows/desktop/dd375731(v=vs.85).aspx documentation] for the full list of virtual key codes defined in the Windows headers.

← Older revision		Revision as of 05:50, 18 February 2017
Line 59:		Line 59:

	Key press and release events are held in a queue in <code>Keyboard</code> in the order they occurred. These events are modeled with their own class because they're precious fucking little snowflakes. They store the type of event (press or release) and the [[#Virtual Key Codes\|virtual key code]] of the associated key. You pull them out of the buffer with <code>Keyboard::ReadKey()</code>.		Key press and release events are held in a queue in <code>Keyboard</code> in the order they occurred. These events are modeled with their own class because they're precious fucking little snowflakes. They store the type of event (press or release) and the [[#Virtual Key Codes\|virtual key code]] of the associated key. You pull them out of the buffer with <code>Keyboard::ReadKey()</code>.
−
−	~~=== Type ===~~
−	~~<code>enum Keyboard::Event::Type</code><br />~~
−
−	~~This represents the different types of events that can be recorded. The options are <code>Press</code>, <code>Release</code>, and <code>Invalid</code>.~~

	=== IsPress ===		=== IsPress ===

@@ Line 4: / Line 4: @@
 <syntaxhighlight lang="cpp" line="1" >
 // how to respond to key release event
 while( !wnd.kbd.IsEmpty() )
+{
 	const Keyboard::Event e = wnd.kbd.ReadKey();
 	if( e.IsRelease() )
+	{
 		if( e.GetCode() == VK_SPACE )
+		{

← Older revision		Revision as of 11:50, 12 February 2017
Line 1:		Line 1:
	With <code>Keyboard</code>, you can get the current state of depressed keys (have a Valium mate), and you can pop key press and release events out of an <code>Event</code> queue contained in <code>Keyboard</code>. You can also turn autorepeat on/off. Whopee. (''Note: the ''<code>kbd</code>'' object lives in ''<code>MainWindow</code>'''s belly.'')		With <code>Keyboard</code>, you can get the current state of depressed keys (have a Valium mate), and you can pop key press and release events out of an <code>Event</code> queue contained in <code>Keyboard</code>. You can also turn autorepeat on/off. Whopee. (''Note: the ''<code>kbd</code>'' object lives in ''<code>MainWindow</code>'''s belly.'')
		+
		+	== Example of Use ==
		+	<syntaxhighlight lang="cpp" line="1" >
		+	// how to respond to key release event
		+	while( !wnd.kbd.IsEmpty() )
		+	{
		+	const Keyboard::Event e = wnd.kbd.ReadKey();
		+	if( e.IsRelease() )
		+	{
		+	if( e.GetCode() == VK_SPACE )
		+	{
		+	// respond to space key release event
		+	}
		+	}
		+	}
		+	</syntaxhighlight>

	== Members ==		== Members ==

← Older revision		Revision as of 02:38, 15 July 2016
Line 1:		Line 1:
−	With <code>Keyboard</code>, you can get the current state of depressed keys, and you can pop key press and release events out of an <code>Event</code> queue contained in <code>Keyboard</code>. You can also turn autorepeat on/off. Whopee. (''Note: the ''<code>kbd</code>'' object lives in ''<code>MainWindow</code>'''s belly.'')	+	With <code>Keyboard</code>, you can get the current state of depressed keys (have a Valium mate), and you can pop key press and release events out of an <code>Event</code> queue contained in <code>Keyboard</code>. You can also turn autorepeat on/off. Whopee. (''Note: the ''<code>kbd</code>'' object lives in ''<code>MainWindow</code>'''s belly.'')

	== Members ==		== Members ==

@@ Line 76: / Line 76: @@
 # Each key press and release sequence puts two events (press event and release event) into the <code>ReadKey()</code> queue, but the same sequence only puts one <code>char</code> value into the <code>ReadChar()</code> queue.
 # The <code>char</code> values read with <code>ReadChar()</code> have the shift modifier applied to them, whereas those read by <code>ReadKey()</code> are just the raw virtual key codes. For example, pressing the 'A' key puts <code>'a'</code> into the <code>ReadChar()</code> queue when the shift key is not pressed and <code>'A'</code> when it is pressed, but the virtual key code in either case is <code>'A'</code> for <code>ReadKey()</code>.
-In general, you should use <code>ReadKey()</code> for controls and <code>ReadChar()</code> for text input.
+In general, you should use <code>ReadKey()</code> for controlling shit and <code>ReadChar()</code> for text input.
 == See also ==
 * The [[Chili Framework]]

@@ Line 21: / Line 21: @@
 <code>bool Keyboard::CharIsEmpty() const</code><br />
 Returns <code>true</code> if the character queue is empty.
 == Event ==