|
ideally, we will get, or collectively build a table which shows for each reader app, how the " read" button in CC is handled.
and for 2 cases ( unless they turn out to have exact same outcomes):
1. CC download folder is in main memory.
2. CC folder is on SD card
a probable further complication: some android versions/devices allow apps to be installed to or moved to SD card
So, the full combinations nightmare to analyse is
location of CC app: internal or on SD
location of reader app: ditto & for each format, if multiple formats/readers are in use
CC download folder: internal or SD
I have made several attempts to read googles files provider/content provider coding rules, which the new CC is trying to adhere to , but they are written for a target audience of expert coders. Let's just say it's messy.
the old CC "read" action just told the reader app where the book file was - no extra copies were made, but google wants to put an end to that behaviour
could be that folks who always (re)opened a book from within CC for reading will have to change their ways
|