-
-
Notifications
You must be signed in to change notification settings - Fork 783
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
Faster filter controls. #438
Comments
How would you list many categories in a segmented control? Sent with GitHawk |
Sessions and Platforms should be fine, because they only have 2 and 4 items respectively. As for Tracks, maybe look to Calendar's show/hide calendar list for inspiration? It would be nice to have all options visible onscreen, and togglable with one click instead of two. |
I've kinda wanted to implement a menu like the constraint addition menu in IB that allows you to hold option to quickly choose multiple values. It would still be a popup button of some kind, but be faster in the case of choosing multiple options. |
Holding modifier keys doesn't seem discoverable, and that still doesn't address the options being hidden until you reveal them. There are a lot of sessions and filtering is very common. I think making it as prominent and fast as possible is a good idea. |
@allenhumphreys Are you going to try it out? I personally don't believe this would work, but I can be persuaded... |
It was just thinking out loud. It seems like a complex thing to implement if there isn’t but in. I am in favor of improving the filtering, though. |
Maybe a menu/shortcut to clear all filters would be a good compromise? |
I feel like that adds another thing to learn, and still doesn't speed things up. It's not clearing filters that needs to be faster, but toggling individual filters. |
Can you use segmented controls instead of popup menus for all filter categories? The [Favorites, Downloaded, Unwatched] filter already uses a segmented control. This would make toggling filters much faster and easier to use.
The text was updated successfully, but these errors were encountered: