BUG: History misbehaves after following a reading plan

4th gen iPad, wifi-only; latest version of the Logos Bible app...

I have a M'Cheyne reading plan (4 passages per day) using the NET Bible. My preferred Bible is ESV. Once I finish the 4th passage for the day (using "Mark Read"), the reading plan takes me to the first passage for the next day. The symptom of the bug is that if I use History at that point (long press) and then touch the ESV entry (usually 1 - 3 entries before the just-read reading plan entries), the app takes me to the ESV but it changes the location to the same passage as it was just on in the NET Bible (i.e. the next day's reading).

If, when I have the history list displayed, I press the "i" icon on the ESV entry to see the passage history within the ESV, it shows the right set of passages. I can press the top passage entry at that point to go to where I expect to end up. But it ought to take me to that location without having to drill down another level.

Hope this explanation is clear.

Donnie

Find more posts tagged with

Mobile App

Comments

Kevin Byford (Faithlife)

4th gen iPad, wifi-only; latest version of the Logos Bible app...

I have a M'Cheyne reading plan (4 passages per day) using the NET Bible. My preferred Bible is ESV. Once I finish the 4th passage for the day (using "Mark Read"), the reading plan takes me to the first passage for the next day. The symptom of the bug is that if I use History at that point (long press) and then touch the ESV entry (usually 1 - 3 entries before the just-read reading plan entries), the app takes me to the ESV but it changes the location to the same passage as it was just on in the NET Bible (i.e. the next day's reading).

If, when I have the history list displayed, I press the "i" icon on the ESV entry to see the passage history within the ESV, it shows the right set of passages. I can press the top passage entry at that point to go to where I expect to end up. But it ought to take me to that location without having to drill down another level.

Hope this explanation is clear.

Donnie

Donnie,

This behavior is by design. I can understand what you mean but other users might find it quite odd when tapping on a different Biblical resource in History that all of a sudden they've lost their place and a different location is opened.

Donnie Hale

https://community.logos.com/discussion/comment/564022#Comment_564022

This behavior is by design. I can understand what you mean but other users might find it quite odd when tapping on a different Biblical resource in History that all of a sudden they've lost their place and a different location is opened.

I've got to say that this doesn't make sense to me. As far as I can tell, in any other scenario where you tap a Biblical resource in History, it goes to the last location you were at in that specific resource. If that's correct, why in this one case would it be better to behave differently?

Donnie

Drew Hannay

https://community.logos.com/discussion/comment/564189#Comment_564189

As far as I can tell, in any other scenario where you tap a Biblical resource in History, it goes to the last location you were at in that specific resource. If that's correct, why in this one case would it be better to behave differently?

When you have a Bible open and you open a different Bible (in any case, not just from History), we try to open the new Bible to the same location as the currently open Bible. In the vast majority of cases, this is the desired behavior...if you're switching from one translation of the Bible to another, you're probably wanting to compare both versions of whatever passage you're currently studying.

Donnie Hale

https://community.logos.com/discussion/comment/564207#Comment_564207

When you have a Bible open and you open a different Bible (in any case, not just from History), we try to open the new Bible to the same location as the currently open Bible. In the vast majority of cases, this is the desired behavior.

I agree that this is the desired behavior in cases where you're opening a different Bible ***from someplace other than History***. The current behavior isn't even consistent with itself. If I use the History dropdown to go back to a different version, it switches from the location that version was at to the location of the then-current version. But if I use a two-finger swipe to go back, it goes back to the location I was previously at in that version.

It's not a huge issue now that I've realized the behavior and can use the "i" icon from the History dropdown. But I disagree with the premise that going to a different version via History means a user wants to go to a different location than the most recent location in that history. (At least this user

Donnie