[chaley]

Originally Posted by PatNY

I've finally had a chance to fully test the new "Read" feature and everything is working perfectly. I made a roundtrip sync, changing values at each stop, from the Nook HD (KitKat) to Calibre and then to my Nook HD+ (ICS) and then back to Calibre, and finally back to the Nook HD. All the new values registered correctly at each stop.

Thanks for this, especially the multi-device tests.

I just have a question regarding the sorting of books in CC. I usually choose to sort by "Date Updated (CC)" with the most recently changed books at the top. I've noticed in this recent round of syncs using Wireless, every book on both devices was given the same new "Updated" date of today. So now they are all randomly mixed up. I gather this was necessary due to the new "Read" feature and database structure? Is there a way to keep the original "Update" dates in the future for books that don't change even when you have to add a new database feature?

--Pat

This is an excellent point, one I am surprised has never come up before. As it is, any time the DB is rebuilt (upgrades because of new versions or changing the custom columns shown in the grouping drawer), the CC changed date gets updated. As you note, this is simply wrong. The fix is easy and risk-free, so I did it. Now the date is changed only when new metadata arrives from calibre.