View Single Post
Old 05-05-2020, 06:26 AM   #10
stumped
Wizard
stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.
 
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
Quote:
Originally Posted by pazos View Post
Just tried the new version.

Some things I noticed:

Target SDK bumped to API 28 (needed to push to Google play store). Still relying on shared storage, no SAF compatible.

They implemented a file provider. That means that CC now ships a hard copy of the book to the reader application. (ie: in MoonReader the book will be copied to attachments even when both apps have permissions to read the same shared storage)...
curious: what will happen if the CC download folder is set to be that same /moonreader/attachments folder
will a 2nd copy be made in the same folder ?

FYI: have been downloading to /moonreader folder then using moon reader's auto add to shelf , then open from moonreader. that avoided issues with CC and moon using different put equivalent syntax to define paths:
/emulated/storage/0 vs /sdcard/

and it also meant I did not also get copies appearing in /attachments
stumped is offline   Reply With Quote