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
Replay search is too complicated #739
Comments
Hmm you might have a point there, but maybe we would need a little more concrete suggestion on how to change. |
I like the search ability with several criteria, but most users probably will only search for Player names and map names. Especially the "contains" filter is handy for obscure player and map names. |
I think it's time to tackle this. @BlackYps already took a shot at it in #1805 but I'm not yet convinced. IMO, one case of "filtering done right" can be seen on digitec.ch. For instance, if you're looking for a graphics card, this is their filter: I think this is what we should aim for. |
These filters are really nice for categories. Maybe we can use the CheckMenuItems for this. But we have to find a way to disable that the menu closes each time you select one Item. I also found this. |
I'm glad this is being looked at. I like the power of the search in general, my hope is that common searches can be made much more quickly and with less clicks. Being able to save particular queries would be useful but if searching is made more efficient that won't be necessary. |
There are lots of essentially useless search terms and too many dropdown menus and items.
The python client search is much better, you have a field for player name, a field for map name, a dropdown to select the base mod(1v1ladder, faf, fafbeta, phantom etc.) and a field for minimum rating.
The text was updated successfully, but these errors were encountered: