How do I correctly qualify event subscriptions with the IPC interface?
Hello everyone,
I am developing a small Python library to communicate with the i3 IPC interface and experience some problems when trying to subscribe to events as described in the official documentation. There the documentation puts the following example for event subscription:
4.1 Subscribing to Events
By sending a message of type SUBSCRIBE with a JSON-encoded array as payload you can register to an event.
Example:
type: SUBSCRIBE payload: [ "workspace", "focus" ]
I take this to mean that I can specifically subscribe to focus events of workspaces. Why else would I want to add "focus" to the payload.
But it seems that - at least for me - there is no difference in the events received between subscribing to ["workspace", "focus"] or subscribing to just ["workspace"].
I first tried to subscribe to "new window" events by supplying ["window", "new"] as payload to the subcription message. But when doing this, I still received messages for any other window change - "focus", "title" and "fullscreen_mode". This did not seem to be different from subscribing to just ["window"]. Therefore my question:
What am I missing?
