Quote:
Originally Posted by chaley
I assume this question arises from experimentation?
My guess is that it is not ignored, but instead the signal message is being tossed because nothing is listening for it on the current event loop. Are you connecting to device_metadata_available? If so, are you using a synchronous connection or a queued connection?
|
I was just using a synchronous connection, but I note that the main library view wasn't changing/toolbars not changing etc when I had any dialogs open. So it appeared that as far as Calibre was concerned the device connection "opportunity" was ignored.
Quote:
|
This means that by definition, you won't support non-drive devices. As I noted above, there is only one such device, but it is possible that some of the Android reader applications might fall into this category.
|
Not entirely - just that I have to "special case" them to support them. Thanks for confirming that iTunes is the only such case currently.
Quote:
|
What? I can't store my books to my SD card? Give me my purchase price back!
|
Yeah I know. But I have seen the question asked a number of times. I wanted to know why Calibre just plain won't support it for news. Perhaps it is something to do with Calibre not storing per device information to even "know" what storage a device should use when sending. After all, this device id stuff was only added relatively recently. I am just curious if there are some scary technical issues I need to be aware of if I allowed users to choose non-main locations.