You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was opened by a bot after a user submitted feedback through the in-app form.
Message:
When I select an application and press Q to quit it, the selection box usually moves forward to the next item.
The exception is if the application selected was the last item in the list. In this case, the selection box in effect moves backward to the previous item (now the new last item in the list).
Can the behavior be made consistent to move the selection box forward always? Or make it an option?
My particular use case is that I see several applications at the end of the list that have had their windows closed but are still running. So I tab over to these applications to quit them by pressing Q. When I am done quitting the last one and let go of AltTab, if selection moved forward to wrap around to the first item, that would put me back into the same window I was in when I started.
But currently, selection moves backward to the last item and it pulls open some random window that I was not working on.
The text was updated successfully, but these errors were encountered:
The current design seems correct to me. Let's see some use-cases (the selected thumbnail is in italic):
Closing many apps which haven't been used for a while, quickly
App 1
App 2
App 3
App 4
Press Q
App 1
App 2
App 3
Press Q
App 1
App 2
Conclusion: This scenario is common, and i think the behavior of keeping the selection close to where it was physically on screen is the most expected / least surprising.
Closing an app in the middle of the list
App 1
App 2
App 3
App 4
Press Q
App 1
App 3
App 4
Press Q
App 1
App 4
Conclusion: In this scenario, I think keeping the selection exactly where it was is the most expected / least surprising.
I understand that you have a different workflow. However, I can't possibly add a preference for every single possible behavior in the app. The preferences would get insanely crowded that way. They are already overcrowded actually (see #351). I'm sorry but please adapt your workflow, or fork the app to support it unofficially. I rarely deny requests, but this one I can't bring myself to green-light.
This issue was opened by a bot after a user submitted feedback through the in-app form.
Message:
The text was updated successfully, but these errors were encountered: