MobileRead Forums - View Single Post

chaley · 08-05-2014, 03:22 PM

CC prerelease 3.4.1a/3.4.1b/3.4.1c has been published and will be available soon. This release contains the following new features and changes over CC V3.4.1:

Remove the newly-added goto FAQ menu item. Instead, add a FAQ button to the "failed to connect" dialogs.
Change text in settings to warn users about CC doing a slow DB upgrade when grouped on lookup names or read info lookup names are changed.
Add "sorted by" information to the top of the grouping drawer.
Allow user to turn on WiFi from within CC. Requires a new permission: change WiFi state.
[3.4.1b]Fix regression in sending books from calibre
[3.4.1c]Fix failure-to-connect regression for devices running pre-KitKat Android releases
[BUG FIX]Do not allow connection to calibre during a DB upgrade. Prevents possible corruption of metadata.
[BUG FIX]Do not reset the book list to the top if read info changes.
[BUG FIX]Make restore settings do a DB upgrade if necessary.
[BUG FIX]Fix problems with syncing read information across multiple libraries.
[BUG FIX]Fix "Send book to app".
[BUG FIX]Fix incorrect month in auto-generated backup file name.
[BUG FIX]Show a better error message when device runs out of space while writing book files.

This prerelease was intended to be a minimal change release to correct the problems with read sync and multiple libraries and a few other small bugs, but events conspired against that. I found several problems where because of what I think are Android bugs, setting a preference in one place was not reflected in another unless the preference screen was closed. The problem was particularly acute concerning changing what is shown in the grouping drawer and then changing autosorts. In addition, Android memory management was causing CC to crash in some circumstances. In addition, detecting out-of-space was more complicated than it should have been. Fixing these problems required changing some basic CC code. Finally, of course I have no self control so I added new features, but fortunately they are close to risk free.

What I ask of testers is simply to use CC, and in particular visit the various settings screens. Thank you all!

My hope is to release this version to production this weekend. We will see.

This release has no DB upgrade.

08-05-2014, 03:22 PM	#1
chaley Grand Sorcerer Posts: 12,449 Karma: 8012886 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	CC prerelease V3.4.1c has been published CC prerelease 3.4.1a/3.4.1b/3.4.1c has been published and will be available soon. This release contains the following new features and changes over CC V3.4.1: Remove the newly-added goto FAQ menu item. Instead, add a FAQ button to the "failed to connect" dialogs. Change text in settings to warn users about CC doing a slow DB upgrade when grouped on lookup names or read info lookup names are changed. Add "sorted by" information to the top of the grouping drawer. Allow user to turn on WiFi from within CC. Requires a new permission: change WiFi state. [3.4.1b]Fix regression in sending books from calibre [3.4.1c]Fix failure-to-connect regression for devices running pre-KitKat Android releases [BUG FIX]Do not allow connection to calibre during a DB upgrade. Prevents possible corruption of metadata. [BUG FIX]Do not reset the book list to the top if read info changes. [BUG FIX]Make restore settings do a DB upgrade if necessary. [BUG FIX]Fix problems with syncing read information across multiple libraries. [BUG FIX]Fix "Send book to app". [BUG FIX]Fix incorrect month in auto-generated backup file name. [BUG FIX]Show a better error message when device runs out of space while writing book files. This prerelease was intended to be a minimal change release to correct the problems with read sync and multiple libraries and a few other small bugs, but events conspired against that. I found several problems where because of what I think are Android bugs, setting a preference in one place was not reflected in another unless the preference screen was closed. The problem was particularly acute concerning changing what is shown in the grouping drawer and then changing autosorts. In addition, Android memory management was causing CC to crash in some circumstances. In addition, detecting out-of-space was more complicated than it should have been. Fixing these problems required changing some basic CC code. Finally, of course I have no self control so I added new features, but fortunately they are close to risk free. What I ask of testers is simply to use CC, and in particular visit the various settings screens. Thank you all! My hope is to release this version to production this weekend. We will see. This release has no DB upgrade. Last edited by chaley; 08-06-2014 at 05:38 AM.