[GUI Plugin] Kobo Utilities

[Majutsushi]

I just released a new version that fixes the error above that happens when using epub files instead of kepub files.

[Majutsushi]

Originally Posted by chaley

Off topic a bit, but ...

At some point when you have nothing else to do , changing the device matching from the UUID in the .driveinfo.calibre to the device serial number if the person is running a version of calibre that has the device_serial_no() method. Using the serial number will prevent losing track of the device if it is reset because the UUID will change but the serial number won't.

Good idea, I'll create an issue for it.

[Majutsushi]

Is anyone still using the "Order Series Shelves" functionality? It seems to be from a time before the firmware supported series tracking natively, and you would have used shelves (now collections) for that instead. Since this should be unnecessary now I'm thinking of removing it to simplify things, I just want to make sure I'm not missing anything.

[Quoth]

I never understood it.
Surely every eink Kobo has series now, though you'd have to load the Mini with Aura FW?

[ownedbycats]

Originally Posted by Majutsushi

Is anyone still using the "Order Series Shelves" functionality? It seems to be from a time before the firmware supported series tracking natively, and you would have used shelves (now collections) for that instead. Since this should be unnecessary now I'm thinking of removing it to simplify things, I just want to make sure I'm not missing anything.

I think when I tried it, it had no effect.

[JSWolf]

Originally Posted by Majutsushi

Is anyone still using the "Order Series Shelves" functionality? It seems to be from a time before the firmware supported series tracking natively, and you would have used shelves (now collections) for that instead. Since this should be unnecessary now I'm thinking of removing it to simplify things, I just want to make sure I'm not missing anything.

That is a very old function. They have not been called shelves for a long time. They are properly called collections. IMHO, any feature labeled as shelves instead of collections should go.

As for my usage, I've never used it. And with series, I see no need for it. Once we got series and support for it, i dropped series based collections.

[PeterT]

Originally Posted by Majutsushi

Looking at how the new DB functionality works by copying data between the device database and a temporary one (using Connection.backup()), I'm not sure the two failing database operations make sense to run on the temporary database. Vacuuming the temporary database should have no effect on the original database since it's not part of the data that would be copied, and similarly with the database checking. So the best thing I can probably do is catch the error and present a friendlier error message.

Edit: Vacuuming may not even be necessary in this situation anyway since the data copying may have a similar effect by its very nature.

Just reminding you to catch the error if possible; seeing this functionality will be in the forthcoming Calibre 8 it would be nice to catch it sooner than later.

[Majutsushi]

Originally Posted by PeterT

Just reminding you to catch the error if possible; seeing this functionality will be in the forthcoming Calibre 8 it would be nice to catch it sooner than later.

Thanks for the reminder, I have actually been working on changing the way the plugin accesses the database to prevent potential data loss if the database has been copied by the new Calibre functionality. I've tested it with both the current stable Calibre and the latest preview release, but since I don't have a Chromebook I can't test the situation where it has actually been copied.

Instead of catching the error the plugin now also disables the two menu options that don't work if it detects that the database has been copied and shows a tooltip about it.

Here is a new build of the plugin with my database changes, it would be great if you (or anyone else) who uses a Chromebook could test that it actually works in that situation. Thanks!

[ownedbycats]

What happened to the upload cover dialog? it looks different and I don't see in the changelog.

[PeterT]

Originally Posted by Majutsushi

Thanks for the reminder, I have actually been working on changing the way the plugin accesses the database to prevent potential data loss if the database has been copied by the new Calibre functionality. I've tested it with both the current stable Calibre and the latest preview release, but since I don't have a Chromebook I can't test the situation where it has actually been copied.

Instead of catching the error the plugin now also disables the two menu options that don't work if it detects that the database has been copied and shows a tooltip about it.

Here is a new build of the plugin with my database changes, it would be great if you (or anyone else) who uses a Chromebook could test that it actually works in that situation. Thanks!

OK. Pleased to see that the compress database and check database menu options are greyed out so no longer available.

THANKS

[Majutsushi]

Originally Posted by ownedbycats

What happened to the upload cover dialog? it looks different and I don't see in the changelog.

I haven't changed anything about uploading covers. What differences are you seeing?

[ownedbycats]

I seem to recall more options like letterboxing.



Is it difference of the Touch and TouchExtended drivers? Only thing I can think of.

[fogice]

Originally Posted by ownedbycats

I seem to recall more options like letterboxing.

Attachment 214466

Is it difference of the Touch and TouchExtended drivers? Only thing I can think of.

You are correct, the old KU has six options (I haven't updated yet, I'm on Calibre 7.24 and Kobo Utilities 2.17.2).

I notice that your screenshot is only showing the options down the left-hand side. Perhaps the size of the window was reduced, and everything else fell off the right-hand side?

[JSWolf]

Does this mean we lose the dithering for covers?

[Majutsushi]

I checked the code and the additional options are behind a dynamic check for Touch devices that broke recently since the check is not picked up by static analysis. I've fixed it and will create a release soon together with the other changes for Calibre 8.

I'm tempted to drop support for non-Touch devices since the dynamic checks necessary to support them risk causing more such bugs in the future. Is anyone still using these ancient devices?