Keyboard raw codes - Revision history

1BitFeverDreams: /* Layout for F256K and F256K2 keyboards */

2025-06-10T13:27:14Z

Layout for F256K and F256K2 keyboards

← Older revision		Revision as of 09:27, 10 June 2025
Line 5:		Line 5:
	=== Layout for F256K and F256K2 keyboards ===		=== Layout for F256K and F256K2 keyboards ===
	The images on the right side were prepared with this website: [https://www.keyboard-layout-editor.com/ https://www.keyboard-layout-editor.com/#/]		The images on the right side were prepared with this website: [https://www.keyboard-layout-editor.com/ https://www.keyboard-layout-editor.com/#/]

	Here are the definition JSON files that can be used in its Raw Data / Upload JSON functionality (use this if you ever need to modify these files as a starting point to your needs)		Here are the definition JSON files that can be used in its Raw Data / Upload JSON functionality (use this if you ever need to modify these files as a starting point to your needs)

1BitFeverDreams: /* Layout for F256K and F256K2 keyboards */

2025-06-10T13:26:58Z

Layout for F256K and F256K2 keyboards

← Older revision		Revision as of 09:26, 10 June 2025
Line 4:		Line 4:

	=== Layout for F256K and F256K2 keyboards ===		=== Layout for F256K and F256K2 keyboards ===
			The images on the right side were prepared with this website: [https://www.keyboard-layout-editor.com/ https://www.keyboard-layout-editor.com/#/]
			Here are the definition JSON files that can be used in its Raw Data / Upload JSON functionality (use this if you ever need to modify these files as a starting point to your needs)

			https://github.com/Mu0n/F256MiscGoodies/tree/main/keycodes


	[[File:F256K and K2 base layout.png\|frame\|Just the keycaps]]		[[File:F256K and K2 base layout.png\|frame\|Just the keycaps]]

1BitFeverDreams: page for keyboard raw codes

2025-06-10T13:18:25Z

page for keyboard raw codes

New page

== Keyboard raw codes ==

These hex codes are part of the events that can be fetched by the [[MicroKernel]] in the event.key.raw data from event.key.PRESSED or event.key.RELEASED events (for more information, see here: [https://github.com/ghackwrench/F256_MicroKernel/blob/master/docs/README.md MicroKernel docs])

=== Layout for F256K and F256K2 keyboards ===

[[File:F256K and K2 base layout.png|frame|Just the keycaps]]

[[File:F256K and K2 with raw keycodes.png|frame|With Raw keycodes in hex]]

=== Example Usage in C ===

(the following is made using the llvm-mos package found here: [[llvm-mos]]

The first step is to fetch the next event in the kernel event queue:
<pre>
kernelNextEvent();
</pre>

Next, verify the pending event with either a switch-case block, or a if:

these two events are relevant to keyboard strokes:

<pre>
kernelEventData.type == kernelEvent(key.PRESSED)
kernelEventData.type == kernelEvent(key.RELEASED)
</pre>

Lastly, this is what must be checked against the raw keycodes listed above:

<pre>
kernelEventData.key.raw
</pre>

ie, this is a proper detection for a 'spacebar' hit:

<pre>
kernelNextEvent();
if(kernelEventData.type == kernelEvent(key.PRESSED))
{
if(kernelEventData.key.raw == 0x20) printf("Spacebar was hit!");
}
</pre>