View Full Version : Fetched News saved to wrong location on Sony PRS-505


shoukyd
02-23-2011, 10:42 AM
Calibre 0.7.46

The generated files are sent to "Device" (i.e. Internal Memory) instead of Card A that I set as the Default (Send to Device -> Set Default Send... -> Send and Delete... -> Card A)

Is there any other setting that I am missing?

theducks
02-23-2011, 10:51 AM
Calibre 0.7.46

The generated files are sent to "Device" (i.e. Internal Memory) instead of Card A that I set as the Default (Send to Device -> Set Default Send... -> Send and Delete... -> Card A)

Is there any other setting that I am missing?



IIRC News is sent to the storage with the most space.

DoctorOhh
02-23-2011, 06:49 PM
The generated files are sent to "Device" (i.e. Internal Memory) instead of Card A that I set as the Default (Send to Device -> Set Default Send... -> Send and Delete... -> Card A)

Is there any other setting that I am missing?

There is no other setting. Calibre autosend of news sends the news to main memory if there is room, if there isn't enough room then it will send it to the SD card.

Release: 0.7.45 [11 Feb, 2011]

New Features


When automatically sending news to device, send to main memory preferentially, if it has enough space. Closes tickets: 8877 (http://bugs.calibre-ebook.com/ticket/8877) http://calibre-ebook.com/site_media//img/external.png

shoukyd
02-25-2011, 05:54 PM
You are right, the behavior changed after the upgrade to 0.7.45
The problem is this:
1) I use the main memory to store items of a more permanent nature.
2) Previously, all the news was sent to the Default (i.e. Card A and deleted from the library). After it was downloaded to the device I would sort it out by date and delete older versions of the news (is there any other way to purge the old versions?)
3) With the new feature, the news goes to the main memory and than overflows to Card A when the main is full. This makes it impossible to sort out the news (its spread on two locations) and delete the old versions. So I need to copy the news back from the main memory to the Library, delete it from the main memory and than transfer it to Card A.
4) Why can't Calibre just use the "Default" setting for downloading news?

shoukyd
02-25-2011, 06:03 PM
Just read ticket http://bugs.calibre-ebook.com/ticket/8877:
It looks like a basic behavior change for everyone just to fix a bug for the Nook.
This also overrides the "Default" mechanism in a very confusing way.
There must be a better way to fix bugs so they don't alter established functionality.

DoctorOhh
02-25-2011, 09:49 PM
2) Previously, all the news was sent to the Default (i.e. Card A and deleted from the library). After it was downloaded to the device I would sort it out by date and delete older versions of the news (is there any other way to purge the old versions?)

Not quite true. While sending it to a default sounds like a good idea, previously it just sent it to the area with the most free memory space.

4) Why can't Calibre just use the "Default" setting for downloading news?

Maybe it can use that setting but it never has before. The only change is now it sends to main memory vice sending it to the area with the most space available. As it stands now if you want it to go to the sd card you can't do it automatically, it must be done manually. Before if you wanted to send it to main memory you had to do it manually.

It looks like a basic behavior change for everyone just to fix a bug for the Nook.

True, now the folks that wanted the news to go to main memory can do it automatically and those that want it sent to the sd card must resort to manual methods. Clearly this is six of one half dozen of the other.

This also overrides the "Default" mechanism in a very confusing way.

Less confusing once you understand it never used the default you refer to in deciding where to send the news.

There must be a better way to fix bugs so they don't alter established functionality.

Established functionality was arbitrary biased toward automatically sending it to the sd card, now it is biased to automatically sending it to main memory.

Maybe you should submit an enhancement request to see if it can be changed to the way you thought it worked.