-
-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Skip "Next/Previous Screen" if no screen detected #196
Labels
Comments
Oh interesting! I just realized that I only tested multi-monitor support when I had an external monitor connected 😅 Also: This is a bug so I'll rename to title to suit that :) |
MrKai77
changed the title
✨ Skip "Next Screen" if no screen detected
🐛 Skip "Next/Previous Screen" if no screen detected
Jan 30, 2024
MrKai77
added a commit
that referenced
this issue
Feb 5, 2024
MrKai77
added a commit
that referenced
this issue
Feb 5, 2024
This should work! |
MrKai77
added a commit
that referenced
this issue
Feb 6, 2024
…if-no-screen-detected` 🐛 #196 Skip "Next/Previous Screen" if no screen detected
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request Description
I noticed that when I disconnect my second monitor, any cycles involving the next monitor action freeze when they reach the point where the window should advance to the next one. I believe that if no secondary monitor is detected, the action should be skipped instead of causing the entire cycle to halt.
Screenshots
003998_1706580454.mp4
Additional Context
No response
Final Checks
The text was updated successfully, but these errors were encountered: