wew returns incorrect data about opt HOT 5 CLOSED

Hello!

Here are a few points:

0. wew expects a number as its mask, not a "name". so wew -m XCB_EVENT_MASK_KEY_PRESS should instead be wew -m 1
1. It is "expected" as the KEY_PRESS event is not handled yet (no plan to do so myself): https://github.com/wmutils/opt/blob/master/wew.c#L175
2. KEY_PRESS is for keyboard events. The mouse pointer triggers BUTTON_PRESS events
3. I don't know what "fsts" in your sentence "it returns fsts on creating a client" means

So to give an answer to your question, I wrote wew for myself, to improve my wmutils experience, and don't plan to do much support for it (because it's a bit hacky and misbehaving). If people send me patches to improve it without breaking it, I can merge them, but I won't do anything myself unless my needs change.

If you provide me a patch that would work for BUTTON_* events, I can probably merge them. Otherwise you can wait for this to, perhaps, be implemented in the future.

from opt.

What event masks are handled by now? Is it only focus and enter events?

from opt.

from opt.

So, as I understand, wew returns cliend ID and the event value as a number. Are there plans to expand the program so that it returns additional data? I, for example, want to know the position of a mouse poiner relative to the screen or the root window(ie root_x, root_y for xlib). In other hand, if wew stands for 'window events watcher' it wouldn't be logical to put such outputs to this one. Or is there any way to get such data using inside a bash script having the wews 'ev' output?
Do not judge me too hard, I am doing this for educational purposes.

from opt.

from opt.