mirror of
https://git.code.sf.net/p/quake/quakeforge
synced 2024-11-23 04:42:32 +00:00
af5d92708d
UI key presses are still handled by regular X events, but in-game "button" presses arrive via raw keyboard events. This gives transparent handling of keyboard repeat (UI keys see repeat, game keys do not), without messing with the server's settings (yay, that was most annoying when it came to debugging), and the keyboard is never grabbed, so this is a fairly user-friendly setup. At first, I wasn't too keen on capturing them from the root window (thinking about the user's security), but after a lot of investigation, I found a post by Peter Hutterer (http://who-t.blogspot.com/2011/09/whats-new-in-xi-21-raw-events.html) commenting that root window events were added to XInput2 specifically for games. Since application focus is tracked and unfocused key events are dropped very early on, there's no way for code further down the food-chain to know there even was an event, abusing the access would require modifying the x11 input code, in which case all bets are off anyway and any attempt at security anywhere in the code will fail, meaning that nefarious progs code and the like shouldn't be a problem. |
||
|---|---|---|
| .. | ||
| audio | ||
| client | ||
| console | ||
| gamecode | ||
| gib | ||
| image | ||
| input | ||
| models | ||
| net | ||
| qw | ||
| ruamoko | ||
| scene | ||
| ui | ||
| util | ||
| video | ||
| Makemodule.am | ||