CC prerelease V3.4.0c

[chaley]

CC prerelease 3.4.0c has been published and will available soon to people who are members of the CC prerelease program.

This prerelease contains the following new features and changes over CC V3.4.0b:

• Add a "splash" activity that is displayed whenever CC must do a database schema upgrade. This avoids "Application Not Responding" errors on very large libraries.
• Add grouped-on custom columns to the sort menu. There is an option to choose which sorts to display
• Add grouped-on custom columns as an auto-sort option.
• Add an option to show/hide the "[autosort by ...]" information in the grouping drawer.
• Show the value being sorted by in the book list. Previously is showed a few dates.
• Remove sending email to us from the Help and About screens. Instead users are pointed toward MobleRead.
• [BUG FIX]Handle custom series, integer, and float columns correctly when sorting and grouping.
• BUG FIX]Fix crash caused by returning to the booklist when first letters had been auto-elided (not shown because there was only one first letter).
• [BUG FIX]Fix order of menu items changing when moved to the system menu.
• [BUG FIX]Fix upload to google books

This release has a database schema upgrade. This is a fast upgrade. In my testing on my original version Nexus 7 it ran at approximately 1000 books per second. You will see the "splash screen" while this is happening. This schema upgrade is backwards compatible.

[kaufman]

You also did:

Perform autosort when jumping to a grouping from a link on a details screen.

------

Installed and played with a few minutes. Two things:

The autosort based on custom column does not seem to be working. The sort dialog is showing the correct sort, but the books are not being sorted.

I'm still getting a crash when I select a tag that starts with an #. I emailed you (but not your son) a debug log.

[chaley]

Originally Posted by kaufman

You also did:

Perform autosort when jumping to a grouping from a link on a details screen.

------

Installed and played with a few minutes. Two things:

The autosort based on custom column does not seem to be working. The sort dialog is showing the correct sort, but the books are not being sorted.

Can you give more information? I tested it with custom series, int, float, and text (single) types and it works fine. It won't work with "text like tags" because there is no control over which tag will be chosen as the sort key.

The book list will show you what value is being chosen for sort, except for text-like tags. If there is no value shown then the book doesn't have a value in that custom column.

EDIT: It will also do nothing if the custom column does not exist in the library.

I'm still getting a crash when I select a tag that starts with an #. I emailed you (but not your son) a debug log.

Will look at it.

[chaley]

Originally Posted by kaufman

I'm still getting a crash when I select a tag that starts with an #. I emailed you (but not your son) a debug log.

My bad. Turns out that constructing the clickable link URLs choke when the first character of the tag isn't alphabetic. It would probably blow up for tags named "&foo" as well.

This time I really fixed it.

[chaley]

Originally Posted by kaufman

The autosort based on custom column does not seem to be working. The sort dialog is showing the correct sort, but the books are not being sorted.

I just thought of something. If the custom column is series, int, or float then unless you do a db rescan the sort values will be wrong. That was one of the bugs I fixed. You can force a rescan by going to settings / make groups from custom columns then taping OK. Perhaps I need to force this as part of the new release.

[jackie_w]

I think something's wrong with sort by Title when using the Sort button.

[chaley]

Originally Posted by jackie_w

I think something's wrong with sort by Title when using the Sort button.

You are right. Sometimes I do very stupid things. I will fix it.

For the interested amongst you; I "improved" a bit of code to eliminate some "if" compares. The code was intended to return "title" sort if it couldn't figure out what else to do. Unfortunately I blew it and it attempted to sort on the category "title" that doesn't exist, so the resulting order is random.

Sigh. Sometimes I think I should leave this coding thing to younger minds ...

[theducks]

Originally Posted by chaley

Sigh. Sometimes I think I should leave this coding thing to younger minds ...

Charles,
I find what you have done with Calibre and CC to be amazing.

Don't beat yourself over a beta that had a logic oops. (I still do those frequently in a lots simpler environment).

Take a breather. Sit back and enjoy a cup'a whatever
The world CAN wait

[jackie_w]

Originally Posted by theducks

Charles,
I find what you have done with Calibre and CC to be amazing.

Don't beat yourself over a beta that had a logic oops. (I still do those frequently in a lots simpler environment).

Take a breather. Sit back and enjoy a cup'a whatever
The world CAN wait

Hear, hear! It's better the beta group find these things than the rabid raters on Google Play.

[Dhevi]

Originally Posted by chaley

You are right. Sometimes I do very stupid things. I will fix it.

For the interested amongst you; I "improved" a bit of code to eliminate some "if" compares. The code was intended to return "title" sort if it couldn't figure out what else to do. Unfortunately I blew it and it attempted to sort on the category "title" that doesn't exist, so the resulting order is random.

Sigh. Sometimes I think I should leave this coding thing to younger minds ...

You put out a magnificent piece of software. You allow input and listen to feedback concerning development.

I feel privileged just to be a part of your process in any way and it can't be said enough, but we appreciate everything you do.

[kaufman]

I'm with everyone else here. We think you are great.

The only silly thing you have done is to think that younger minds don't also make silly coding errors.

By the way, my issue about custom columns not sorting was the same bug related to title sorting. When I switched it to author sort it worked perfectly.