View Single Post
Old 10-25-2012, 08:26 PM   #4
jackie_w
Wizard
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 2,710
Karma: 3818505
Join Date: Sep 2009
Location: UK
Device: Sony PRS-350, PB360, Kobo Glo/AuraHD/Aura6"
After some playing around I'm OK with the 'db' part of your reply but not the 'device' part. I understand, using your example, that I can do things like
Code:
device=PRS505(None)
print(device.EBOOK_DIR_MAIN)
to view some variables, but if I want to be able to examine other device data available whilst the device is actually connected to my PC, what extra do I need to do?
e.g within a plugin, if I wanted to know what drive the device was connected as I would use
Code:
root_path = self.gui.device_manager.connected_device._main_prefix
what extras would I need to import to be able to access this data via the commandline?
jackie_w is offline   Reply With Quote