quakeforge/ruamoko/qwaq/qwaq-input.r

#include "ruamoko/qwaq/qwaq-input.h"

void init_input (void) = #0;
void send_connected_devices (void) = #0;
qwaq_devinfo_t *get_device_info (int devid) = #0;
[qwaq] Add input test app The queues in the curses resources struct have been cleaned up and the threading support code (including for the queues (pipes, really)) has been moved to its own file. The input test app currently just prints the devices and the events as they come in, but demonstrates the new input system working in a separate thread (though it is currently in with the curses thread). 2021-09-21 03:58:10 +00:00			`#include "ruamoko/qwaq/qwaq-input.h"`

[qwaq] Move input handling to its own thread As it is now a completely separate sub-system, there is a bit of trouble with mouse handling in that curses must be initialized before input for the mouse to work properly, but the basic scheme seems to be working nicely. I suspect the solution to the init order issue is to make have the curses sub-system initialize the terminal input driver, at least for mouse input (ie, maybe just enable/disable mouse handing). 2021-09-22 07:22:11 +00:00			`void init_input (void) = #0;`
[qwaq] Add input test app The queues in the curses resources struct have been cleaned up and the threading support code (including for the queues (pipes, really)) has been moved to its own file. The input test app currently just prints the devices and the events as they come in, but demonstrates the new input system working in a separate thread (though it is currently in with the curses thread). 2021-09-21 03:58:10 +00:00			`void send_connected_devices (void) = #0;`
			`qwaq_devinfo_t *get_device_info (int devid) = #0;`