[GUI Plugin] Reading Goal

[ownedbycats]

Question:



Is there a way to change the date of the first 0% record other than manually tampering the JSON or removing and re-adding the book to the goal?

[thiago.eec]

Originally Posted by ownedbycats

Is there a way to change the date of the first 0% record other than manually tampering the JSON or removing and re-adding the book to the goal?

Yes. In the book list, change the date to the correct value (without changing the progress). Then, go to "Edit Goal > Show book records" and delete the old entry.

[ownedbycats]

The new date doesn't appear as a separate record, and I can't delete the only entry.

[thiago.eec]

I've just tested here:

1) Added a book to my reading goal on 07/23, with no progress
2) Today I changed the date to 07/25
3) Now, when I press 'Show records', I see both records there
4) Then, I can delete the 07/23 entry

[ownedbycats]

Ah, it works for me now - there's a weird little UI quirk where the record displays in the same row as the book record which confused.

[ownedbycats]

I ran into another weird glitch:



I added a #lastread of 2024-01-01 to several backlogged books. However, two specific books keep erroring. I tried removing them and re-adding them and noticed that it tried to add to 2023 instead.

The only odd thing I can think of is perhaps some timezone shenanigans as the other books don't have 00:00:00:



EDIT: It is the exact time. If I copy the date from a non-glitched book (which also includes the specific time information) it doesn't error.

[Comfy.n]

hmm, I wonder why your exact date doesn't display the milliseconds bit before the timezone, which amusingly is the same.

[ownedbycats]

Maybe a regional formatting thing?

[thiago.eec]

Originally Posted by ownedbycats

I ran into another weird glitch:

Attachment 209765

I added a #lastread of 2024-01-01 to several backlogged books. However, two specific books keep erroring. I tried removing them and re-adding them and noticed that it tried to add to 2023 instead.

The only odd thing I can think of is perhaps some timezone shenanigans as the other books don't have 00:00:00:

Attachment 209766

EDIT: It is the exact time. If I copy the date from a non-glitched book (which also includes the specific time information) it doesn't error.

I don't know if this is some sort of calibre setting, but I can't get my date field to accept just the date, without the time info. When I begin to edit the field, calibre already sets the time to 00:00.

Also, when I set the date to '2024-01-01 00:00:00-03:00', and add the book to my reading goal, the year selected is 2024, not 2023.

How did you get calibre to set the date without the time info? Maybe using the Action Chains plugin?

[theducks]

Does it freact to one of these Tweaks?

# Control how dates are displayed

gui_pubdate_display_format = 'MMM yyyy'

gui_timestamp_display_format = 'dd MMM yy, hh:mm'

gui_last_modified_display_format = 'dd MMM yy hh'

[thiago.eec]

Originally Posted by theducks

Does it freact to one of these Tweaks?

# Control how dates are displayed

gui_pubdate_display_format = 'MMM yyyy'

gui_timestamp_display_format = 'dd MMM yy, hh:mm'

gui_last_modified_display_format = 'dd MMM yy hh'

If I understand it correctly, those are used in the book list, but not in the metadata dialog. The screen capture posted was from the metadata dialog.

[theducks]

You may be correct. My GUI timestamp has been adjusted to only show HH

I sure don't need to worry about Min and Sec ...I am RETIRED

[ownedbycats]

Originally Posted by thiago.eec

How did you get calibre to set the date without the time info? Maybe using the Action Chains plugin?

Action Chains, I think.

My screenshot was a tooltip from the MDE. A few updates ago it was added to show the full timestamp there.

[thiago.eec]

Originally Posted by ownedbycats

Action Chains, I think.

I think that's the problem. Action Chains does this directly via python, so it can add the date without the time info. Then, when the -3h offset is applied, the record is placed in 2023 instead of 2024.

A solution would be to use 2024-02-01.