-
Notifications
You must be signed in to change notification settings - Fork 181
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
[gm/ObjectCreationView] Allow filtering/sorting ship lists #1932
Comments
So sorting the list by class and subclass is indeed pretty straightforward, by fetching the class and subclass along with the template name and then extending the sort to sort by class first, then subclass, then alphabetically: But the interface for the sorted result isn't as straightforward. Those "headings" are fake entries that create the next listed ship. GuiListbox doesn't provide headings or separators. Without the fake headings, the list is even harder to parse than when it's sorted only alphabetically, unless you already know what the classes are (in which case, you don't need to sort by class). So the question is, is it better to use one list and make sorting more flexible - which could retain the default behavior for those who want it, but also requires extending GuiListbox to allow headings, which might also help with #1925's problem of organizing ships in the science DB - or is it better to make the ship list paged using a GuiSelector, which would add more clicks/taps each time the GM wants to add a ship? |
Not sure if this is possible: What about "sorting" selector under CPU/player ship selector, which will enable sorting: Extending GuiListbox with headings could be nice. There would be then potential to extend functionality with collapse/expand option (that will collapse/expand all items under this heading up to next heading). That could also be useful in science DB (collapsing sub-classes that are useless to science officer for quick analysis of possibilities might be nice). |
Splitting from #1926.
@hemmond:
@oznogon:
The text was updated successfully, but these errors were encountered: