View Single Post
Old 04-18-2011, 03:29 PM   #7
chaley
"chaley", not "charley"
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 5,802
Karma: 1216080
Join Date: Jan 2010
Location: France
Device: Many android devices
Code pushed.

The signal is device_metadata_available, and is raised after all the connection processing is complete. It should be visible to a plugin as gui.device_metadata_available.

The sequence: gui.device_manager.is_device_connected will become True, then sometime later gui.device_metadata_available will be signaled. This does not mean that there are no more jobs running. Automatic metadata management might have kicked off a sync_booklists to write new metadata onto the device, and that job might still be running when the signal is emitted.
chaley is offline   Reply With Quote