View Single Post
Old 05-13-2014, 10:53 PM   #4
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 29,817
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by kovidgoyal View Post
The problem is that many usb devices do not have unique identifiers, so it is not possible in general to ribustly distinguish between them. So while one could use a kludge like using the driver plugin as a proxy or putting a device id into the driveinfo.calibre file, these kinds of solutions are fragile and rather confusing.
I can see it being slightly fragile.
I can also see that the current (method) setting would be used (unless it fell into the STD or CTF group) as a default until detected and set, Similar to the way device {Templates} work
theducks is offline   Reply With Quote