Quote:
Originally Posted by At_Libitum
like Faterson already implied without probably realizing, you still would need to download it...
|
Spare me that, please.

I
explicitly addressed what you're talking about, so I fail to see how I could "not have realised it". Like I said: pushing a single cloud button on 3 iDevices is no big deal! It's
not annoying or time-consuming. But having to go through the entire rigmarole of a long series of manual steps and many taps in various places, just to import every new book manually 3 times on 3 iDevices, is definitely annoying and time-consuming.
I also reject the rephrasing of the original request, moved to another thread now:
https://www.mobileread.com/forums/sho...d.php?t=227595 Like we said, we wish to use the
current Marvin Library interface (no OPDS, the Dropbox plugin or web browsers), but without the requirement to store
any book locally. That is, it should not be a requirement for a book to be locally present in
any Marvin library; the book could be
in the cloud only, while it would still show up in all Marvin Libraries on all iDevices, available for a single-tap download at any time.
Also, it has been stressed numerous times that putting your Marvin Library into the cloud would be
100% optional. If you don't like the feature, don't use it, and continue manually keeping your multiple local Libraries in sync on all your iDevices like you do now. That strikes me as a very inefficient workflow, but if you prefer it over an
optional cloud-based Library, by all means stick to the current library (or I should say libraries) management method.
Quote:
Originally Posted by fireland
I figured out that "force quit" means turn off the device.
|
It doesn't; no need to turn off the device. It's enough to close Marvin from the multi-tasking screen by swiping it up out of view.
Quote:
Originally Posted by Lancer_325
I lost my full library so will have to start from scratch.
|
You never had to lose anything. Marvin always gives the user the option to perform a full backup of everything, regardless of which Marvin version you may be running. In your eagerness to get the new Marvin version up and running immediately,

you acted a bit too fast without thinking of those disagreeable consequences, unfortunately.