Thread: Wish for Device Driver mount point
View Single Post
Old 03-11-2025, 01:35 AM   #48
Majutsushi
Zealot
Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'
 
Posts: 111
Karma: 10128
Join Date: Aug 2023
Location: New Zealand
Device: Kobo Clara HD, Kobo Libra Colour
Quote:
Originally Posted by kovidgoyal View Post
device driver functions are called in a single non-GUI thread. Not to mention that there is only one temporary location per driver instance.
What about plugins? I'm particularly thinking of the Kobo Utilities plugin, which has some feature that allow users to modify the device database, and which currently uses its own database connections. Is there a way to make sure that those features don't run at the same time as other device driver functions? I'm not very familiar with the Calibre internals so I'm not sure how likely this scenario is.
Majutsushi is offline   Reply With Quote