-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
Add hotkeys / shortcuts for filters #573
Comments
This is an automated response. We acknowledge your report, and we appreciate your engagement. However, as there has been no recent activity in this thread, it has been marked as stale. If you have any further feedback or if the matter is still relevant, please do not hesitate to respond. Otherwise, this thread will be automatically closed in 15 days from now. |
@stephprobst do you have a proposal in mind, which shortcuts could make sense? Especially considering those will need to be implemented cross-platform and should be scalable, since there will be more filters in the future. |
I would have chosen CTRL + T to toggle visibility for items with threshold dates in the future. This shortcut is usually used for "new tab", which shouldn't be a relevant shortcut for sleek I guess? |
To keep it consistent, we would then need to reserve CTRL + D for due dates. And once more filters come along we will run out of shortcuts, which are not yet mapped by conventions or operating systems, quite quickly. And since sleek supports tabs, I can't rule out there is never going to be a need for CTRL + T to create a new tab. |
Feature Request
Description:
In Sleek 1.* there were shortcuts for filter to quickly toggle visibitly for threshold dates in the future and completed todos. It would be great to have the shortcuts again for all of the available filters:
Implementation Details:
There are already a shortcut for
Completed todos
in theTodos
context menu of the application. (See screenshot below)It would be great to simply add the remaining filters there.
The text was updated successfully, but these errors were encountered: