CC production release V3.5.9 has been published

[chaley]

Change log:

• Increase book limit on demo version to 20
• [BUG FIX]Fix show read info on book list option also hiding the option in book details
• [BUG FIX]Fix sporadic crash when returning to the book list/grid

[kaufman]

I'm not sure if this is new or not, I have a column called pages which contains the page numbers in each book.

It does show the correct number in the book list, but in the book details page it just shows "%," for each book.

[chaley]

Originally Posted by kaufman

I'm not sure if this is new or not, I have a column called pages which contains the page numbers in each book.

It does show the correct number in the book list, but in the book details page it just shows "%," for each book.

My guess is that this is an integer or a float custom column with a provided number format, and that that number format isn't valid in CC's terms. A change in 3.5.9 changes CC's behavior in this case. Before, it applied a default format. Now it simply prints the format string.

Sending me a debug log will help determine whether this is a problem on CC's side (i.e. I messed up the translation of python formats to Java) or a problem in the format entered into the custom column definition.

[kaufman]

Sent.

My guess is that in this one case it isn't my error, or else why would it show the correct value in the List view.

[chaley]

Originally Posted by kaufman

Sent.

My guess is that in this one case it isn't my error, or else why would it show the correct value in the List view.

The book list shows the value as supplied by calibre, without attempting to format it. Book details attempts to format the value. This is in fact a bug in the list view stuff, because it is ignoring the format.

According to the debug log, the format is something like "{:,}". It could also be "%,". Both are invalid. What does calibre show in the column definition for that column for the format?

[kaufman]

It shows: {0:,}

[chaley]

Originally Posted by kaufman

It shows: {0:,}

This is indeed a CC bug, caused by my misunderstanding of format defaults. In python, "{0:,}" for any number column is equivalent to "{0:,d}" where the "d" means decimal number. I didn't account for this default in CC.

There are two possible fixes:
1) You change the column definition to {0:,d}. Of course, this will force a full metadata calibre->CC send on the next connect.
2) I change CC to detect this special case. I will do this, but it may be a few weeks before I make another release.

In case it matters, {0:,} will not work correctly in calibre for floating columns because the default is to format as integer.

[kaufman]

Well, you can change eventually it if you want, but I am happy to do a full metadata refresh to save you the trouble.

I believe that this is the default for a custom integer column, so others might run into this.

[chaley]

Originally Posted by kaufman

Well, you can change eventually it if you want, but I am happy to do a full metadata refresh to save you the trouble.

I will fix it, simply because it should be fixed. However, it won't be released for a bit unless some new crashes show up.

I believe that this is the default for a custom integer column, so others might run into this.

The default is empty (no format).