-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
marvin XD does not reload when books are added #12
Comments
Please create a debug trace. |
calibre 1.3 isfrozen: True is64bit: True DEBUG: 14.8 ERROR adding to installed_books DEBUG: 14.8 ERROR adding to installed_books DEBUG: 15.0 ERROR adding to installed_books DEBUG: 15.1 BookStatusDialog:_purge_cover_hash_orphans() |
I believe this is the same problem as #14. Please reopen this bug if you see the behavior again. The fix is available in version 1.0.4. |
I'm still having this happen in 1.0.4. Do you need another stack trace? |
Please post another debug log, it has to be a different error as I fixed the one in original debug log. |
calibre 1.3 isfrozen: True is64bit: True |
There are no errors in the debug log, so let's go back to your original workflow:
I followed these exact steps and I am seeing the added book when reopening the MXD window as expected. When the MXD window opens, you can sort on different columns, so depending on how you have things sorted, you may not be seeing the book where you expect it. If you toggle the 'Show|Hide match status' button a couple of times, it will reset the sort order to put matched (green) books on top. Is it possibly not where you expected to see it? Please check the book count (in the MXD title window) before and after downloading the book. Did it go up by one? |
Nope, the count does not go up unless I disconnect and reconnect Marvin. (I've been resorting by author to double check before that the book was not there). My books are also coming over as match status yellow (with no differences showing on 'View metadata') |
Try updating to 1.0.5 |
The book that you're downloading - does it already exist in Marvin? |
The books I'm adding do not exist in my Marvin for iPhone. They are on my Marvin for iPad (which is not currently connected during this morning's tests) 1.0.5 might have fixed the books coming over as matched yellow. 1.0.5 did not fix MXD not reloading after syncing a book |
Please try this with your iPhone connected and the calibre connector running: |
One more thing to try. I'd like to see a debug log from iOS reader applications when you're doing the transfer. With Marvin connected, go into the Device context menu and open the Config dialog. Enable plugin debugging. For now, disable debugging in MXD. Restart calibre, capture a debug log, post it. This will show what's happening when sending the book to Marvin. |
For the first time, I did not need to disconnect Marvin for Marvin XD to see the new book I copied over. It did come over as matched status yellow however. (huh, I never sent this last night) This is a debug log from sending a book (for what this may or may not be worth). Sorry that I haven't had a chance to debug in the last few days. I do have a question: I have an issue with Marvin XD which might be behind why books are syncing as match yellow. I get the same issue when using my OPDS calendar. I have edited the book's meta data in calibre so that the author sorting is correct. I even use 'Polish books' to update the meta data in the book. However, Marvin still gets the book with the wrong author sort. Do you know why this is? calibre 1.3 isfrozen: True is64bit: True |
The debug log indicates that your book is in fact being added to Marvin correctly.
Both the OPDS download and the direct plugin download use the current calibre metadata and apply it to the copy of the book being sent. Please create step-by-step documentation of what you're doing and what you're observing so that I can try to replicate it. If I can replicate the issue, I should be able to resolve it. Here's the steps I took to try to replicate your problem:
This works for me as expected. |
I'm closing this issue as there's been no followup. |
The text was updated successfully, but these errors were encountered: