Lots of unknowns here still, but current strategy has a while(true) loop that waits for user input. so this means user text input is the only event minwm is "listening" for.
instead, what would be way better, is to have a socket where events of all types could come in, and minwm would respond accordingly. this is better because it allows for more types of events e.g. user requests keyboard, user rotates screen, process requests focus (like functionality you would expect when the phone rings), and other events that haven't been thought up yet.
trent234
commented
4 years ago
Lots of unknowns here still, but current strategy has a while(true) loop that waits for user input. so this means user text input is the only event minwm is "listening" for.
instead, what would be way better, is to have a socket where events of all types could come in, and minwm would respond accordingly. this is better because it allows for more types of events e.g. user requests keyboard, user rotates screen, process requests focus (like functionality you would expect when the phone rings), and other events that haven't been thought up yet.