Quote:
Originally Posted by chaley
The device driver plugins cannot use/depend on GUI interaction, so the file's default contents must be determinable without user input. If someone wants to write GUI code to alter the file's contents, a basic write API can be provided.  My guess is that you want a library ID, not the calibre installation ID.
What is a volume ID, and where did it come from? |
It is the optional use part of the Windows/linux File system.
I name all my SD/pen drives/HD partitions. eg.
Code:
C:\Documents and Settings\shop1>vol
Volume in drive C is C-clamp
Volume Serial Number is F857-3467
P:\>vol
Volume in drive P is BOOKS1
Volume Serial Number is 8483-EA81
P: is my device SD card
I think all FAT volumes have a serial ID
Quote:
What is "book list match" and where did it come from? My guess is that it the information is already in metadata.calibre
|
Correct.
I was suggesting one way to ID the (device) storage (with a damaged ID file) was a fast compare with the snapshots in the archived 'on device libraries'. Not perfect. If it reached a threshold of 'hits', the user could be queried: 'Is this Charlies PRS-300?'
Quote:
The device ID will be a UUID assigned by calibre. Many devices don't have a built-in ID, and I have no interest in figuring out how to get the ID for devices that do but that I don't own. If such a thing is necessary, someone else can take on this challenge.
There would be such a file on each memory location.
|