Removed code to zero reports between two keyboard reports with differing number of pressed keys, as this relied on non-standard OS behaviour.

1 files changed, 2 insertions, 11 deletions

diff --git a/Demos/Device/LowLevel/Keyboard/Keyboard.c b/Demos/Device/LowLevel/Keyboard/Keyboard.c
index 33a6d840a..4e7921f70 100644
--- a/Demos/Device/LowLevel/Keyboard/Keyboard.c
+++ b/Demos/Device/LowLevel/Keyboard/Keyboard.c
@@ -258,11 +258,11 @@ void EVENT_USB_Device_StartOfFrame(void)
  */

 void CreateKeyboardReport(USB_KeyboardReport_Data_t* ReportData)

 {

-	static uint8_t PrevUsedKeyCodes;

-	uint8_t UsedKeyCodes      = 0;

 	uint8_t JoyStatus_LCL     = Joystick_GetStatus();

 	uint8_t ButtonStatus_LCL  = Buttons_GetStatus();

 

+	uint8_t UsedKeyCodes      = 0;

+

 	/* Clear the report contents */

 	memset(ReportData, 0, sizeof(USB_KeyboardReport_Data_t));

 	

@@ -281,15 +281,6 @@ void CreateKeyboardReport(USB_KeyboardReport_Data_t* ReportData)
 	  

 	if (ButtonStatus_LCL & BUTTONS_BUTTON1)

 	  ReportData->KeyCode[UsedKeyCodes++] = 0x09; // F

-	

-	/* The host will ignore the device if we add a new keycode to the report while another keycode is currently

-	 * being sent (i.e. the user has pressed another key while a key is already being pressed) - we need to intersperse

-	 * the two reports with a zeroed report to force the host to accept the additional keys */

-	if (UsedKeyCodes != PrevUsedKeyCodes)

-	{

-		memset(ReportData, 0, sizeof(USB_KeyboardReport_Data_t));

-		PrevUsedKeyCodes = UsedKeyCodes;

-	}

 }

 

 /** Processes a received LED report, and updates the board LEDs states to match.