Calibre Companion prerelease 3.3.0c

[Dhevi]

Originally Posted by chaley

I am very willing to make it "Read" instead of "Marked Read".

Anyone else have comments? Alternatives?

Why not perhaps... "Mark as Read"?

Edit:
::Looking at the post above this one:: That's what I get for not having read through the entire post lol. Carry on. Carry on.

[kaufman]

Glad you said that, because mark as read is even worse.

[Dhevi]

I'm having difficulty with the Marked Read option.

I have a custom yes/no column establised in Calibre 1.26 for identifying read books. When connecting with CC as a wireless connection for the first, and any subsequent syncs, the Marked Read field remains empty, and instead Calibre #read is set to Blank for the book series I am testing with.

Even given that issue, marking the book as read through CC, and then syncing as wireless with Calibre, the custom column is not updating to reflect "yes". The Date read does update without any issue when selecting mark read in CC, and in Calibre, but I'm having difficulty with syncing read status.

[kaufman]

This might be a silly question, but did you set up the column names in the settings?

[chaley]

Originally Posted by Dhevi

I'm having difficulty with the Marked Read option.

I have a custom yes/no column establised in Calibre 1.26 for identifying read books. When connecting with CC as a wireless connection for the first, and any subsequent syncs, the Marked Read field remains empty, and instead Calibre #read is set to Blank for the book series I am testing with.

Even given that issue, marking the book as read through CC, and then syncing as wireless with Calibre, the custom column is not updating to reflect "yes". The Date read does update without any issue when selecting mark read in CC, and in Calibre, but I'm having difficulty with syncing read status.

In CC's settings check the spelling of the lookup name of the calibre yes/no column. You will get something like the behavior you describe if what you put in CC doesn't exactly match what is in calibre, including letter case.

I have changed both CC and calibre to do this check and tell you if the lookup names are not correct (don't exist in the connected-to calibre library) or if the types of the custom columns are not correct. I can't release the CC changes until the calibre changes are available, which could be as far as Friday.

[Dhevi]

Thank you Kaufman and Chaley for your responses. In working backwards with your input, I found, that in fact, my custom column "read" was not a "yes/no" field, but rather a "text" field... hence my difficulty in syncing properly.

Thanks plenty to both.

[LadyKoori]

I've been hoping CC would allow for syncing of a Read column since I first started using it last year. I love it for syncing with my library! Any idea of when you'll be releasing 3.3.0 to the world?

[kaufman]

Been playing with the syncing on my Galaxy Note 3 and LG pad 8.3 using calibre 1.26. No issues to report. Everything related to the read column seems to be working perfectly. I haven't played much with the date stuff yet so I can't comment on that.

Still hoping you just go with "read" for the label.

[chaley]

Originally Posted by Dhevi

Thank you Kaufman and Chaley for your responses. In working backwards with your input, I found, that in fact, my custom column "read" was not a "yes/no" field, but rather a "text" field... hence my difficulty in syncing properly.

Thanks plenty to both.

You are welcome. Glad you got it working.

The problem you ran into is exactly why I have added checking the column type when you connect. Given that a person can connect to several libraries, that is the only place I can reliably do the checks. CC will display a pop-up message during connection saying what is wrong.

[chaley]

Originally Posted by LadyKoori

I've been hoping CC would allow for syncing of a Read column since I first started using it last year. I love it for syncing with my library! Any idea of when you'll be releasing 3.3.0 to the world?

I will release what I hope is the last prerelease on Friday once calibre 1.27 is available. If all goes well for several days, then I will probably make the general release (it will be 3.3.1) to Google Play on Wednesday 12/March (or thereabouts), with the release to Amazon soon after. If things don't go well, and especially if I need to change something in calibre, it could be the week after.

[chaley]

Originally Posted by kaufman

Been playing with the syncing on my Galaxy Note 3 and LG pad 8.3 using calibre 1.26. No issues to report. Everything related to the read column seems to be working perfectly. I haven't played much with the date stuff yet so I can't comment on that.

Good.

Still hoping you just go with "read" for the label.

In the next release (3.3.0d) it looks like the attachments in post 14. The label is "Read".

[kaufman]

Chaley:

One small issue and on comment on a screen.

1) It looks like the program is appending the Calibre book id to the book filename even when that feature is turned off. Or does "Use Book ID as filename" only use the ID?

2) The screen to change the book storage directory is a little odd. I wanted to move my book library to the external SD card, and I couldn't find a way to do it without manually entering the directory name. When I bring up the dialog box it shows "/storage/emulated/0" and there doesn't seem to be a way to move up the tree. I also think you might want to add a confirmation before you start moving the files in case someone click on the "(Use the Folder)" by accident. Otherwise, someone stupid (like me for example) might hit it by accident and start moving their books to the wrong folder.

[chaley]

Originally Posted by kaufman

1) It looks like the program is appending the Calibre book id to the book filename even when that feature is turned off. Or does "Use Book ID as filename" only use the ID?

It uses the calibre unique id (UUID) as the filename. This isn't the relatively short number, but is instead a 36-character string that looks something like 550e8400-e29b-41d4-a716-446655440000 (thanks, wikipedia). Using this string guarantees that the file name is identical whether the book was loaded from the content server or the wireless device, something that is useful if you are syncing reading positions between multiple devices. Of course, it does make the file names useless for manual browsing, but that shouldn't be necessary.

If that option isn't set then the file name for books sent via the wireless device connection is controlled in the file template calibre settings of the wireless device. For the content server the name is fixed at something like {title} - {author}; I don't remember exactly.

2) The screen to change the book storage directory is a little odd. I wanted to move my book library to the external SD card, and I couldn't find a way to do it without manually entering the directory name. When I bring up the dialog box it shows "/storage/emulated/0" and there doesn't seem to be a way to move up the tree. I also think you might want to add a confirmation before you start moving the files in case someone click on the "(Use the Folder)" by accident. Otherwise, someone stupid (like me for example) might hit it by accident and start moving their books to the wrong folder.

The problem is that there is no standard naming convention for SD cards, so we can't give a list of them. In addition, some SD cards are read-only, and so on. We decided early on not to attempt to deal with the issues.

That said, you could have entered "/" and then navigated down. I have changed the dialogs to (I hope) make that more obvious and to make a distinction between creating a folder and navigating to one. The "manual change" is now "change folder", and the path you enter must exist and be a folder. It is pre-filled with "/".

We will see if this is better.