[chaley]

Originally Posted by kaufman

FYI, I actually only got the crash on #. Tags that started with underscore worked fine.

I am quite sure that tags starting with ? or & would also fail. Perhaps '='. Basically characters that mean something in URLs.

One thought I had today. Since you have already done all the work to extract and use the custom tag name in the sorting and grouping menus, would you consider adding a dialog to the settings to allow people to rename them to something more readable? It would make several places a lot prettier. I was thinking that the simplest thing for people to understand would be a two stage process. Step one would be to list the custom columns as they do now, and step two would be to fill in a translation table. Or maybe just turn the custom column stuff into the translation table.

This is in the wish list as "Some way to add a display name for custom columns in the grouping drawer". You are right to point out that having the autosorts etc expands the scope of the wish but it doesn't change the fundamentals.

What I intend to do is to change the groupable items entry dialog to use key/name pairs, such as "#genre/Genre, #series/Reading order". If you don't enter a /... then the display value will be the key. For existing installations I will migrate the keys to the display values.

I hope to have this in the next release.

Last thought. Since custom columns are. Now group able, does it make sense to make them clickable in the book details screen?

Probably.

Originally Posted by jackie_w

@chaley,

If someone chooses to autosort a grouping by Author, would it be possible to (silently) actually sort by Author/Series/Title. Would there be any harm? Based on a lot of the early work with metadata plugboards, I think it's probably a common sort preference and it would be very convenient (especially for me )

Just to be clear, I'm not suggesting that choosing Author from the standard Sort button would do this (even if I'd prefer it this way), just the autosort.

This is a difficult one for me. On one hand I can see why you want it and why others might want it. On the other hand it introduces magic behavior and could break someone's carefully-prepared sorting sequence, neither of which are desirable.

Regarding your example, why bother with Title? Do you have books with the same series and series index? Ahh... you are dealing with the case where there is no series, in which case Title would effectively become the second sort key.

Kaufman's idea to introduce some compound sorts would eliminate the magic, but it would also increase pressure to be able to create them dynamically or to have several of them. Being able to take sorts off the menu removes a big reason to avoid having lots of them.

So the question: other than Author/Series/Title, are there any other compound sorts that scream for attention?

Related question: is there any reason to have "Read" as a sort?

Originally Posted by DoctorOhh

No, it sorts by series name and THEN series number.

Piling on now.