Closed glutanimate closed 2 years ago
Likely related to #108. Both issues might be fixable at the same time.
Please consider not removing completely the current behavior (maybe letting to choose in the config). I just love using the new reschedule feature, and setting whatever new interval I need (instead of using anki's algorithm) but keeping track of my "reviews" in your add-on.
@glutanimate do you think this bug is something inherit with how the heatmap calculates reviews or a more minor fix? I will start to look into this. The correct stats (unaffected by rescheduling) calculated by the base Anki code seem to be tied into the Rust back end. I am not familiar with Rust, so if anyone who works with Rust would like to take a look at this it would be much appreciated.
Hey guys,
This should now be fixed with v1.0.0 which I just released on AnkiWeb (no need for a manual installation any more, you can just copy the add-on code into Anki as with other add-ons.)
Basically, you can now configure whether the add-on takes rescheduled/forgotten cards into account or not (the default being that they aren't counted as repetitions). The setting can be found in the Fine Tuning tab in Review Heatmap's options.
Hope that helps! And if you run into any issues please do let me know.
Cards rescheduled via Anki's new rescheduler might be counted as reviews in the heatmap at the moment, as reported here for instance: https://reddit.com/r/Anki/comments/mbgb6u/review_heatmap_counts_reviews_when_using_set_due/
The more desirable behavior would be to ignore rescheduling entries in the review log (if they can be identified as such). Will have to look into the new rescheduling code to see if that's the case.