Dov Grobgeld

The question is whether the keyboard modifiers are really a state of "another device", or perhaps a global state of the system? E.g. in qt, all input events have access...

Meanwhile I worked around this issue by querying qt about the modifier state: ``` Qt::KeyboardModifiers qtmodifiers = QGuiApplication::queryKeyboardModifiers(); ``` But I still think there should be supported by vsg itself....

Isn't the global keyboard modifier state accessible from all major OS's? A quick search turned up the following: - https://www.x.org/releases/X11R7.7/doc/libX11/XKB/xkblib.html#Keyboard_State - https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getkeyboardstate So there doesn't seem to be a reason...

Here is another relevant piece of information, that I think is relevant to the discussion. I mapped the zoom/pan/rotate behavior of a common commercial program that I would like to...

Here's how you differentiate between a mouse event and a stylus event in gtk+3.0: ``` gboolean on_event(GtkWidget *widget, GdkEvent *event, gpointer user_data) { GdkDevice *device = gdk_event_get_device(event); GdkInputSource source =...

> Please see `copilot-chat.el` https://github.com/chep/copilot-chat.el I'm using copilot-chat.el to have an interactive chat session with copilot. However I am not aware that I can select something in a source code...