Open Gemba opened 1 year ago
Do you have hints/ideas how to track this down? Maybe it is also related to the allegro lib itself.
FWIW. As a workaround the allegro 5 build can be used. However, this limits the usage to the Raspberry Pi 4, as the Raspberry Pi 3 and the Head-over-Heels allegro5 binaries are not performing well together.
cf. https://gist.github.com/Gemba/f2c541f6e027d7278e948f80e311e318#file-headoverheels-sh-L46
Such “the keyboard works in menus but not in the game” I am sometimes suffering (but sometimes not, it looks really random) when I run the game thru gdb
(the debugger)
@Gemba I’m sure you’d like the 6dd444c301d73012eff29b9fd821c031f88caf4c patch
as for the issue with keyboard, that’s what I’ve got
keys are handled in two distinct threads, those which control the game and those which control the characters
so anything that treats threads unequally may broke the key handling
the good news are that since C++11 there’s std::thread
https://en.cppreference.com/w/cpp/thread/thread
does anyone want to try porting thread handling to std::thread
, maybe?
Describe the bug On a Raspberry Pi the binary can be started and shows up the menu. In the menu navigation works with keyboard controls but after starting a new game the keyboard events are no longer recognized.
Allegro Lib Tested with 4.4.3.1 (bundled with this repo) as well as with 4.4.2.1 from Raspi OS Buster.
To Reproduce Steps to reproduce the behavior:
headoverheels
, navigate to new gameExpected behavior Keyboard should be usable in game.
Testsystem
Additional context
PS: Thanks for reviving this classic game and gem.