[GUI Plugin] Reading Goal

[ownedbycats]

Also, just for futureproofing: When 2025-01-01 rolls around, what will happen to any migrated unreads that have a 2024 #lastread? Will they also error?

For reference, I'm adding the current datetime to #lastread before adding it to the goal. for sorting purposes, mostly.

[thiago.eec]

Originally Posted by ownedbycats

Also, just for futureproofing: When 2025-01-01 rolls around, what will happen to any migrated unreads that have a 2024 #lastread? Will they also error?

Let's break it down:

1) 2024-01-01 works just fine here, so 2025-01-01 will work too. Like I said, maybe the problem is how the date was set (via Action Chains). When you set a datetime via python, you can choose to use a naive datetime or a timezone aware. My guess is that Action Chains uses a naive datetime object, but calibre adds the offset, putting it in the wrong year.

2) If you use the RG auto migrate feature, the books in your 'want to read' and 'reading' shelves will be moved to your 2025 goal in 2025-01-01. But you'll still need to change your #lastread date to 2025, since the plugin never touches your calibre library.

[beedaddy]

I'm currently testing the plugin and have noticed that the genre column keeps getting forgotten. I can select "tags" as the genre column in the settings, but the next time I open the settings it has disappeared again. Have I perhaps missed something?

[thiago.eec]

Originally Posted by beedaddy

I'm currently testing the plugin and have noticed that the genre column keeps getting forgotten. I can select "tags" as the genre column in the settings, but the next time I open the settings it has disappeared again. Have I perhaps missed something?

That's a bug. Thanks for reporting it. I'll investigate.

[thiago.eec]

Version 1.6.0 - 06 Aug 2024

- Bug fix: avoid the genre column being cleared when using a standard field (tags)

[beedaddy]

Thanks a lot. I can confirm that the problem has been fixed.

[ownedbycats]

Enhancement, if feasible: An option to further group books in Edit Reading Goal per month.

[thiago.eec]

We would need another column just for that, taking space of other columns. You can already sort it by date, so I don't think it is worth to compromise the current layout.

[ownedbycats]

Here's an odd behaviour I was able to replicate:

1. Have a goal book with a null date and a progress of 0.
2. Change date to the current date. This now results in two entries in the reading goal.



3. Then update progress. Unless the undated 0% entry is deleted, the dated 0% entry disappears.



Is this intended?

[thiago.eec]

1) When you add a book to your goal, the current date/progress will be registered as you your first record

2) A new record is created only when you change the progress. If you check your json, at this point, you will see this:

"records": {
        "0": {
          "date": null,
          "read_pages": 0,
          "status": 0
        }
      },

The main entry is not really a record. It is constantly updated, reflecting the information in your calibre library. If you change any of the metadata, the Edit Reading Goal dialog will be updated too. So, you'll see the new date, but no new record was created.

3) Here you updated the progress, hence got a new record. Now you json looks similar to this:

"records": {
        "0": {
          "date": null,
          "read_pages": 0,
          "status": 0
        },
        "1": {
          "date": {
            "__class__": "datetime.datetime",
            "__value__": "2024-08-15T10:23:50.830000+00:00"
          },
          "read_pages": 3,
          "status": 1
        }
      },

P.S.:

Originally Posted by ownedbycats

Unless the undated 0% entry is deleted, the dated 0% entry disappears.

When delete your only record, then the plugin creates a new record based on you current data, because there must be at least one record all the time.

[sandrilea]

Thank you for this plugin. It's really awesome! I just found it about two weeks ago and want to keep reading so I can enter more data .

If I go to the Genre view in edit reading goal and click on the date column in order to sort by date I get the following error:

calibre, version 7.16.0
FEHLER: Unbehandelter Ausnahmefehler: <b>TypeError</b>:'&lt;' not supported between instances of 'QDateTime' and 'NoneType'

calibre 7.16  embedded-python: True
Linux-5.15.0-116-generic-x86_64-with-glibc2.38 Linux ('64bit', 'ELF')
('Linux', '5.15.0-116-generic', '#126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024')
Python 3.11.5
Interface language: de
EXE path: /app/lib/calibre/bin/calibre
Traceback (most recent call last):
  File "calibre_plugins.Reading_Goal.main", line 3337, in __lt__
    return first < second
           ^^^^^^^^^^^^^^
TypeError: '<' not supported between instances of 'QDateTime' and 'NoneType'

In shelf view there is no problem sorting by date.

Thank you for your great work!

[ownedbycats]

Originally Posted by thiago.eec

1) When you add a book to your goal, the current date/progress will be registered as you your first record

2) A new record is created only when you change the progress. If you check your json, at this point, you will see this:

"records": {
        "0": {
          "date": null,
          "read_pages": 0,
          "status": 0
        }
      },

The main entry is not really a record. It is constantly updated, reflecting the information in your calibre library. If you change any of the metadata, the Edit Reading Goal dialog will be updated too. So, you'll see the new date, but no new record was created.

3) Here you updated the progress, hence got a new record. Now you json looks similar to this:

"records": {
        "0": {
          "date": null,
          "read_pages": 0,
          "status": 0
        },
        "1": {
          "date": {
            "__class__": "datetime.datetime",
            "__value__": "2024-08-15T10:23:50.830000+00:00"
          },
          "read_pages": 3,
          "status": 1
        }
      },

P.S.:


When delete your only record, then the plugin creates a new record based on you current data, because there must be at least one record all the time.

Ah, that makes sense.