Open cwqt opened 2 years ago
(This should may be a separate issue and/but maybe irrelevant in light of the #73 Rewrite either way; I didn't become aware of the rewrite in progress until after I typed all of below:)
On Monterey beta 5 (21A5304g), and I believe also on earlier betas, on M1 it seems to actually stay permanently stuck to the Space its opened on :( - regardless of switching method (ctrl+arrows, touchpad swipes, via mission control)
with -m config debug_output on
it seems to be ~correctly receiving EVENT_HANDLER_SPACE_CHANGED
Going off https://github.com/cmacrae/spacebar/issues/82#issuecomment-883020100 , I tried seeing if -m config spaces on
would prompt a repaint on (now) active space, but it does not
-m config display all
or -m config display main
does though
(This should may be a separate issue and/but maybe irrelevant in light of the #73 Rewrite either way; I didn't become aware of the rewrite in progress until after I typed all of below:)
On Monterey beta 5 (21A5304g), and I believe also on earlier betas, on M1 it seems to actually stay permanently stuck to the Space its opened on :( - regardless of switching method (ctrl+arrows, touchpad swipes, via mission control)
with
-m config debug_output on
it seems to be ~correctly receivingEVENT_HANDLER_SPACE_CHANGED
Going off #82 (comment) , I tried seeing if
-m config spaces on
would prompt a repaint on (now) active space, but it does not
-m config display all
or-m config display main
does though
Yeah for me it's permanently stuck on the first space. I'm on Monterey on an M1 Pro. Any idea what I could try to fix this :)?
Using cmd+1/2/3/4.... to switch desktops (bound in Keyboard Shortcuts > Mission Control) causes spacebar to disappear for a split second, not a huge issue just a noticeable thing - using cmd+left/right doesn't cause this issue
https://user-images.githubusercontent.com/61694629/129759650-4dba45b2-3cd0-46b8-af6c-34d7d3b2620f.mov