editor open wrong book when showing books on device

[theducks]

Originally Posted by BetterRed

I think edit-book does too. See Edit->Preferences->Integration with calibre->Update metadata in book when opening - the default value is checked

Can't recall what it does to the metadata, it's here somewhere. I have it unchecked.

=============================

One of the things I've noticed about the editor is that I can't easily determine the path of the file that its editing - a Properties/Summary option in File would be nice. Sigil doesn't have it either, however it's Save As option assumes same location as the file under edit.

BR

Having a 'Properties' under File would be the place that was consistent with Windows . BTW THis also is the place where metadata for MP3 (and other media) files can be seen/set

[BetterRed]

Originally Posted by theducks

Having a 'Properties' under File would be the place that was consistent with Windows . BTW THis also is the place where metadata for MP3 (and other media) files can be seen/set

Hmmmm, maybe I'd settle for something similar to np++, put path in Title bar and/or in a simple popup a'la it's View->Summary option.

Having File->Properties might make people think its yet another metadata editor, a'la Word & PDF XChange.

BR

[kovidgoyal]

Originally Posted by BetterRed

I think edit-book does too. See Edit->Preferences->Integration with calibre->Update metadata in book when opening - the default value is checked

That setting applies only when you open books from the calibre library from within calibre. It does not apply when you run the editor standalone as in this case.

[davidfor]

Originally Posted by DiapDealer

I understand the desire to warn about using caution when editing a file on the device, but there's nothing "really" dangerous about it. It won't hurt the device at all, and the file on the device is hardly going to be considered the master copy/backup of the ebook (even under the weirdest of circumstances)--especially if calibre is being used by the end-user. I say experiment away! Just keep good backups.

As the others have said, Kobo devices have some problems with this. I mentioned this because I know cybmole has just bought one.

There are two problems:

- If the file size changes, then current firmware will remove all info about the book from the internal database and then add it as a new book. This means you lose the reading status and shelves it is on. Older firmware deleted the book and the database records. If a book is resent from calibre, the driver will update the size in the database to prevent this from happening.

- When the book is first seen, the metadata is extracted and stored. With this is the TOC from the NCX. If the structure of an epub is changed or the TOC updated, it doesn't get reread. This will cause problems when reading the book. The most likely problem is that it won't reopen in the right spot. But, in past firmware, it could cause a crash.

[PeterT]

Originally Posted by davidfor

- When the book is first seen, the metadata is extracted and stored. With this is the TOC from the NCX. If the structure of an epub is changed or the TOC updated, it doesn't get reread. This will cause problems when reading the book. The most likely problem is that it won't reopen in the right spot. But, in past firmware, it could cause a crash.

If the SIZE has changed, wouldn't this be a non issue, since the book would be purged from the DB and then reread?

[eschwartz]

Well, you will get an error message now if you try to do it.

https://github.com/kovidgoyal/calibr...176177c1eda3c8

[davidfor]

Originally Posted by PeterT

If the SIZE has changed, wouldn't this be a non issue, since the book would be purged from the DB and then reread?

Except that if you resend using calibre, the driver updates the file size in the database. At the time I did this, the books were getting deleted completely and not re-added. Plus, if you are only change the text or styles, it is safe.