IsKeyPressed for some keys not working on RPi (PLATFORM DRM)

[larry104]

I notices that the block of keys (insert, delete home, end, pup, pdown) are not working. IsKeyPressed is not getting any event for these keys (I tried different keyboards and started the application from ssh terminal vs native terminal no difference). All other keys are working fine. Does anyone have an idea what is going wrong ?

[ghost]

@larry104 Could be this https://github.com/raysan5/raylib/blob/master/src/platforms/rcore_drm.c#L167-L173 or this https://github.com/raysan5/raylib/blob/master/src/platforms/rcore_drm.c#L146-L164 I think.

Edit: editing.

[larry104]

Well, it might not be that but thanks to your link to the specific source code it might be this:

raylib/src/platforms/rcore_drm.c

Lines 1334 to 1374 in a3a73b9

	{
	if ((keysBuffer[i + 2] == 0x5b) || (keysBuffer[i + 2] == 0x31) || (keysBuffer[i + 2] == 0x32))
	{
	// Process special function keys (F1 - F12)
	switch (keysBuffer[i + 3])
	{
	case 0x41: CORE.Input.Keyboard.currentKeyState[290] = 1; break; // raylib KEY_F1
	case 0x42: CORE.Input.Keyboard.currentKeyState[291] = 1; break; // raylib KEY_F2
	case 0x43: CORE.Input.Keyboard.currentKeyState[292] = 1; break; // raylib KEY_F3
	case 0x44: CORE.Input.Keyboard.currentKeyState[293] = 1; break; // raylib KEY_F4
	case 0x45: CORE.Input.Keyboard.currentKeyState[294] = 1; break; // raylib KEY_F5
	case 0x37: CORE.Input.Keyboard.currentKeyState[295] = 1; break; // raylib KEY_F6
	case 0x38: CORE.Input.Keyboard.currentKeyState[296] = 1; break; // raylib KEY_F7
	case 0x39: CORE.Input.Keyboard.currentKeyState[297] = 1; break; // raylib KEY_F8
	case 0x30: CORE.Input.Keyboard.currentKeyState[298] = 1; break; // raylib KEY_F9
	case 0x31: CORE.Input.Keyboard.currentKeyState[299] = 1; break; // raylib KEY_F10
	case 0x33: CORE.Input.Keyboard.currentKeyState[300] = 1; break; // raylib KEY_F11
	case 0x34: CORE.Input.Keyboard.currentKeyState[301] = 1; break; // raylib KEY_F12
	default: break;
	}
	if (keysBuffer[i + 2] == 0x5b) i += 4;
	else if ((keysBuffer[i + 2] == 0x31) || (keysBuffer[i + 2] == 0x32)) i += 5;
	}
	else
	{
	switch (keysBuffer[i + 2])
	{
	case 0x41: CORE.Input.Keyboard.currentKeyState[265] = 1; break; // raylib KEY_UP
	case 0x42: CORE.Input.Keyboard.currentKeyState[264] = 1; break; // raylib KEY_DOWN
	case 0x43: CORE.Input.Keyboard.currentKeyState[262] = 1; break; // raylib KEY_RIGHT
	case 0x44: CORE.Input.Keyboard.currentKeyState[263] = 1; break; // raylib KEY_LEFT
	default: break;
	}
	i += 3; // Jump to next key
	}
	// NOTE: Some keys are not directly keymapped (CTRL, ALT, SHIFT)
	}
	}

since I only see F keys and up down left right keys. The scan codes for (insert, delete home, end, pup, pdown) are not mapped and are 4 byte long in contrast to 5 bytes for F keys and 3 bytes for cursor keys.

e.g. insert key is
^[[2~ 27 0033 0x1b
91 0133 0x5b
50 0062 0x32
126 0176 0x7e

Was there a reason not to add these keys?

[ghost]

Was there a reason not to add these keys?

@larry104 Probably just overlooked.

[larry104]

Can this thread be converted into a bug/feature request or do I need to file this under issues?

[ghost]

@larry104 Sure, there's a "Create issue from discussion" button on the right side of the page.

[larry104]

doh ... didn't see that sorry. Thanks a lot!!!