Problems with KeyDown event and Raspberry Pi bookworm

Targets Raspberry Pi
1

My application uses Window KeyDown event to collect characters from keyboard / barcode scanner.

It works well with Raspberry Pi Buster system but doesn’t work with Bookworm one…

Like no characters detected…:confused:

Any ideas?

2

Are you in Wayland window-Manager? May it makes a difference in X / WaylandX.

3

Well, I suppose I am not. This is “legacy” bookworm installation with desktop on Raspberry Pi 3B, nothing more. My app is just desktop app with single full-screen / maximized window.

I put some “collect character one by one” code in windows’ KeyDown event and it doesn’t collect anything. The same software runs on previous version of OS (buster) and this works well, when run under MacOS - works too.

4

Bookworm defaults to Wayland i read. May you can switch back to X11 and check. In older Linux this was possible in the login screen.

5

I have switched between all 3 options; X11 among them. No KeyDown input:(

6

OK, Wayland works, too… the only difference is that under Bookworm You cannot leave any BevelButton with Allow focus set to true. If there is any BevelButton (perhaps any object with Allow focus option) - it becomes “in focus” and the window doesn’t get any input - all KeyDown events go to the object with focus. Strangely, it wasn’t a problem before…?

7

I think there’s an issues ticket about this. I know it’s come up before. On mobile or I would be more helpful.

8

The BevelButton is a good example under Bookworm:

  • when pressed - it stays graphically in pressed state / value = true and doesn’t switch back to normal state. I had to set its state to false in Pressed event to make it click back :wink:
  • If this BevelButton has ability to receive focus - it stays focused all the time.

Due to above mentioned observations I think the real problem is that BevelButton doesn’t have ability to auto deactivate, despite this option being set to true.