CC Prerelease V3.4.0e & V3.4.0f

[Dhevi]

Perhaps i spoke a too soon.

I have Counts shown and when viewing the group drawer for READ before I would be presented with three items. YES, NO and <<>> for no entry in the Read field. I neither receive a Count or the leafs under the READ branch. Of the 119 books in CC I know 3 to be unread with no entry and 116 with YES. Nothing major. Just something I noticed.

[Purple Lady]

Originally Posted by Dhevi

Perhaps i spoke a too soon.

I have Counts shown and when viewing the group drawer for READ before I would be presented with three items. YES, NO and <<>> for no entry in the Read field. I neither receive a Count or the leafs under the READ branch. Of the 119 books in CC I know 3 to be unread with no entry and 116 with YES. Nothing major. Just something I noticed.

I have 3.40d on my T168 and all three items are there.

[kaufman]

Originally Posted by Dhevi

Perhaps i spoke a too soon.

I have Counts shown and when viewing the group drawer for READ before I would be presented with three items. YES, NO and <<>> for no entry in the Read field. I neither receive a Count or the leafs under the READ branch.

Check your settings. Are the fields related to read books still filled in?

[Purple Lady]

Originally Posted by kaufman

Check your settings. Are the fields related to read books still filled in?

Read info is still filled in on my Nexus 7 where I see the same problem.

[Dhevi]

Originally Posted by kaufman

Check your settings. Are the fields related to read books still filled in?

Yes they are. I checked to make certain that the READ field on at least 15 books is still filled in. The only change between when it displayed last to now, was pre 3.4. I am currently running 3.4.0f.

Edit: I should clarify. When last I noticed this present was when I was still using the prior release. It wasn't until 3.4.0f that I noticed the count for READ was missing.

[chaley]

Originally Posted by kaufman

1) The "fast upgrade" took about 30 minutes. Would it be possible to show the book x of y process here as well as in the notification? Might be useful.

There is something very strange happening here. I just tried an upgrade on a library with 1250 books and it took 39 seconds, or 32 books per second. If your device ran at the same speed that would mean you have 57,000 books on your device, which I know you don't.

Is your main memory almost full? That could cause SQLite to alter how it does the update, although I don't know that it would.

[chaley]

Originally Posted by Dhevi

Perhaps i spoke a too soon.

I have Counts shown and when viewing the group drawer for READ before I would be presented with three items. YES, NO and <<>> for no entry in the Read field. I neither receive a Count or the leafs under the READ branch. Of the 119 books in CC I know 3 to be unread with no entry and 116 with YES. Nothing major. Just something I noticed.

Originally Posted by Purple Lady

I have 3.40d on my T168 and all three items are there.

Originally Posted by Purple Lady

Read info is still filled in on my Nexus 7 where I see the same problem.

This is definitely a regression. The Read group is never subject to first-letter grouping, and that check went away. Fixed in next release.

The Read group works on the current release if you turn off first-letter grouping.

[kaufman]

Originally Posted by chaley

Is your main memory almost full? That could cause SQLite to alter how it does the update, although I don't know that it would.

Nope, about 7gb free.

[chaley]

Originally Posted by kaufman

By the way, I have a small request that I am perfectly happy to move to the wish thread if it is too much trouble, but I wanted to mention here in case it wasn't. Would you be willing to add an option to select the app orientation to be:

1) Free (ie Match system setting)
2) Portrait only
3) Landscape only

I use the app in bed a lot and I regularly have to turn off screen rotation to keep it in portrait mode. I would prefer to have it always stick to portrait mode.

I know you said you were done with functionality changes, but you spoiled me on the last release with all your extra effort, plus you owe me for all the abuse I got in the 3.4.0d release.

Originally Posted by theducks

I just turn off the (Android) auto rotation, but I could see locking in one plane as is good after playing Multipies Puzzles (paid version)

Built it. The preference screens look like the following:

[jackie_w]

I'm late to the party but what a treat this release is! My perfect sort options plus no more Book Details superfluous fields clutter on my phone.

The only problem I've found so far is that the Book Details item 'Formats on device' doesn't show when it's checked. It won't bother me because I won't be using it but I thought I'd report it.

Also a consideration for a future release. On my Samsung Galaxy TabPRO even the 'Large' Book Details cover size is only 4.5x3cm because the screen resolution is, 2560x1600. As more tablets get the higher res screens perhaps an extra-large option may be popular.

[kaufman]

Originally Posted by jackie_w

The only problem I've found so far is that the Book Details item 'Formats on device' doesn't show when it's checked. It won't bother me because I won't be using it but I thought I'd report it.

Shoot. I meant to post this yesterday but I forgot. I saw (or rather didn't see) the same thing. I only have epub on my devices so perhaps it only shows up with more than one format.

[kaufman]

Originally Posted by chaley

Built it. The preference screens look like the following:

Love it. You are the greatest.

[chaley]

Originally Posted by jackie_w

The only problem I've found so far is that the Book Details item 'Formats on device' doesn't show when it's checked. It won't bother me because I won't be using it but I thought I'd report it.

Originally Posted by kaufman

Shoot. I meant to post this yesterday but I forgot. I saw (or rather didn't see) the same thing. I only have epub on my devices so perhaps it only shows up with more than one format.

That field never should have been there. It is shown only in the content server. It will go away in the next release.

[chaley]

Originally Posted by jackie_w

Also a consideration for a future release. On my Samsung Galaxy TabPRO even the 'Large' Book Details cover size is only 4.5x3cm because the screen resolution is, 2560x1600. As more tablets get the higher res screens perhaps an extra-large option may be popular.

There be a few dragons here.

CC doesn't have the original cover defined in calibre. Instead it has a computed thumbnail, 320x320 maintaining aspect ratio. We can certainly increase the amount of screen real estate taken by the displayed image, but that could easily pixelate. For example, in portrait I can imagine you wanting the cover in a 600x600 box. Lets call that 640x640, which means that every cover image pixel is expanded to 4 displayed pixels. I don't know if this is acceptable. If the displayed PPI is very large than it probably wouldn't matter.

The alternative is to increase the size of the downloaded thumbnail. The upside is a nicer picture. The downside is substantially longer download times and substantially more memory (database) use. In addition, every cover would be downloaded on the next wireless connect any time the preference was changed. I am very reluctant to go down this road.

A third alternative is a variant of the first: pick a "standard" PPI, perhaps for example that of the original N7/N10, and scale the cover image so that the physical space consumed on higher density devices is the same as on the "standard" device. This might be the right choice, but unfortunately I have no way to test it because I don't own a high-density device. There is also the potential problem of pixelation.

I am not sure what the right approach is.

[chaley]

@jackie_w: looking at the code I find that I already scale the image by the comparative pixel density (the third option I discussed).

Two things:
1) Could you send me a debug log from the TabPRO? It shows the density calculations that CC uses. Please erase the multipie email address, as my son doesn't need to get involved in this.

2) Are you running landscape or portrait? Do you have the same "too small" impression on both modes?

Thanks.

EDIT: also note that covers are 5cm high on my Galaxy Nexus and my Nexus 7. It could be that what we should do is scale by density and also screen size, so that the cover takes a known percentage of the (for example) screen width.