{"ops":[{"insert":"It seems strange to me to be able to sort by color but not by type. I often want to categorize by Color Tag, and then sort by Color because it lines up with how my staples binder is organized, but then lands are mixed in with artifacts and colorless spells because the secondary sorting method is always alphabetical. my Chrome Mox comes in the list between Bloodstained Mire and Command Tower and then Mana Crypt is further down.\n\nI know you can't support everyone's different styles and wants or needs, this one in particular just seems a bit strange from an organization standpoint to lump the artifacts in with the lands just because they are technically colorless, alphabetical just seems like the wrong secondary choice especially since when people import decks or are deck building the default way of grouping cards is by type first, then alphabet.\n\nWhen I think about most \"list management\" or \"database management\" tools, a common piece of functionality is also to \"remember\" the last selected sort method and allow the user to build the sort order in reverse. Example: fields are name, category, color, quantity. User clicks on the Quantity header of the table, and it sorts the whole list by Quantity and that's it. User than clicks on the qame category, and the list is sorted by Name first, and quantity second. User than clicks on category header and list resorts by category first, name second and quantity third. User than clicks on color and the list is sorted by color > category > name > quantity. You maintain this as a Stack collection (last in first out) and if a user selects a header that's already been selected or double clicks a header it moves it to the front and clears the list. The size of the stack varies from application to application, some have only 2 deep some have 3 and rarely 4, but you've already got the hard work done of writing all the sorts.\n\nTLDR; Could we change the Sort function to be prioritized by:\nUser selected setting."},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"Category."},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"Alphabet."},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"Or: Remember the user's last selected sort order and use that for the secondary sort method rather than alphabetical, two dimensions would be wildly better than just one.\n\nP.S. Kudos though on putting the lands with an actual color identity in with the other cards of that color, I could have seen that as something easily missed.\n"}]}
0
{"ops":[{"insert":"I'm a bit confused. I think what you're asking for is when ordering stacks of cards by color, you want them to use card type as a secondary sorting rather than alphabetical? I could see this being useful, though maybe a bit confusing at a glance. I think I'd want to see it in action before we make any choices on that though. \n\nThe problem (like you alluded to), is how much do we want to support tertiary, etc, ways of sorting -- at some point it just clutters up the UI. Otherwise I'd agree in that we should just allow you to keep adding sorting methods arbitrarily. \n\nWe looked into caching user selected options for a bit, but we never really gave it it's time to really attempt to push for that. Instead what we opted for was allowing users to set their default sort settings in their account settings. If you do that then it'll default to those every time. I couldn't really tell from your comment whether or not you knew about these, so I figured I'd give those a shout out here. \n\nLooking forward to hearing your thoughts on the comments above. Thanks so much for the comments! \n"}]}
0