Improve yabai event-based stack

[alin23]

Unfortunately the flicker is still there and it is caused by reacting to the window_destroyed event on Hammerspoon canvas windows.

I hope we can fix this in Hammerspoon itself by using the standard AXUnknown subrole for its windows to have them filtered out by yabai.

[AdamWagner]

Quoting from our convo on #13

About the flicker, it is caused by the window_destroyed signal which does not have an app!= filter to filter out Hammerspoon window events.
…
But of course, this means that closing a window leaves the stackline with a window that does not exist anymore.
Until I can think of a proper solution, I'm working around that by adjusting the yabai gap size which triggers a window_resize event and recreates the stack

Trading flicker for failing to update when a window is destroyed seems like kind of a sideways move. It could be argued that changing the focused window (and inducing flicker) is so much more common than closing/removing a window from a stack that it's worth it, but I'm not so sure. The flicker is annoying, but at least predictable.

I think I'm going to leave this one open until we figure out if #8 has legs (which will hopefully occur next weekend).

[alin23]

@AdamWagner this should be automatically fixed if this yabai PR is merged: koekeishiya/yabai#636

[alin23]

Change of plans, it would be better to fix this in Hammerspoon itself: Hammerspoon/hammerspoon#2427

[alin23]

@AdamWagner could you please review this again when you have some time? 😊

[AdamWagner]

Really great idea to move the yabai signals out of the readme and into a version-controlled file 👍

I see that the Hammerspoon PR is still open. So, does this mean that a user must build Hammerspoon locally to run this branch? Apologies if I'm missing something obvious…

Hammerspoon/hammerspoon#2427

[alin23]

I was hoping that the yabai PR would get merged to ignore hs.canvas windows until the Hammerspoon one is merged and released.

[AdamWagner]

Ah gotcha. I saw the comment thread on the yabai PR, and it doesn't look like it's not going to happen any time soon. If not having this merged is making it harder for you to develop further, I'll merge it, but I don't see a reason to merge it otherwise.