[resolved] Reading plan progress: jumping backwards
I have several books that I'm reading presently with a Logos reading plan; these particular books have graphics, either old black and white graphics, or cartoons.
I've notice quite a few times that when I get to the end of the day's reading and click on "Done," the next day's reading will appear by jumping backwards. Thus in part consecutive days will have the same paragraphs.
Strange. Don't know if the graphics are involved, but this issue especially seems to be so for these resources.
Comments
-
Philip Larson said:
Strange. Don't know if the graphics are involved, but this issue especially seems to be so for these resources.
This may be the case - I reported the same bug about a year ago and Faithlife thought it was a resource issue - what was not discussed back then: the book in question has some cartoons in it. Maybe your report now helps Logos to find and fix the bug (or regression).
Have joy in the Lord!
0 -
I don't ever use reading plans in L6 (except to create them), but I have seen this behavior on mobile (iOS). It happens to me frequently.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Bump - 3ax
Dave
===Windows 11 & Android 13
0 -
NB.Mick said:Philip Larson said:
Strange. Don't know if the graphics are involved, but this issue especially seems to be so for these resources.
This may be the case - I reported the same bug about a year ago and Faithlife thought it was a resource issue - what was not discussed back then: the book in question has some cartoons in it. Maybe your report now helps Logos to find and fix the bug (or regression).
So the case that you created last year was resolved, and we never followed up with you. Apologies for that. [:(]
Apparently this is an unfortunate side effect of the way page milestones are handled in our resource markup. The problem is that there are various uses for having the milestones set up this way, and it's in place in many, many resources and has been used for a long time. At this point, the effort to fix this issue is bigger than the problem (and could potentially create more issues).
0
