Your results when flipping backwards in Bible

One thing that makes the iOS interface less than stellar to me is that when I flip backwards to a previous page, the last line on the page is not necessarily the last line before where I was at on the page I flipped from. The result is that when I flip back to original page, what was the start of that page is no longer at the top. This is a deviation from the page-turn metaphor.

Also, my reading plan is OT,NT, Psalms & Proverbs each session. I don't get consistent results on what displays as I go to each session. For example. The OT reading might start with 'Chapter X' at the start of display, but Psalms generally does not. It starts with the introductory material or first verse, but not the chapter #.

Looking for consistency. Can anybody else reproduce?

Thanks,

Stuart

Find more posts tagged with

Mobile App

Comments

Ron

Yes, I've seen that as well...though it may be an iOS issue because I've seen the Kindle app do the same thing when moving backwards through a Bible.

Todd Phillips

https://community.logos.com/discussion/comment/381299#Comment_381299

Yes, I've seen that as well...though it may be an iOS issue because I've seen the Kindle app do the same thing when moving backwards through a Bible.

Actually the Logos 4 Windows application does this too, when you set a window to column mode. I think the reverse page calculation isn't completely accurate, and the same algorithm is used for all platforms. Since Kindle does it too, then maybe accuracy isn't quite possible (or isn't possible if you want good performance).

Alan Palmer (Logos)

https://community.logos.com/discussion/comment/381307#Comment_381307

New features added to our display engine (which you will be seeing in the future if you use the FSB) introduced some complications to our page size calculations.

We've made some improvements to this recently. However, one thing to note is that if you change the size of the display (e.g. rotate your device, move the divider, or resize the window on desktop, etc) all bets are off. Also, if you jump somewhere in the resource we clear the page size information (so paging up after a jump will generally be a worst case scenario).

It is our goal for paging forward and back to put you right back where you were, so feel free to continue to report these issues if you see them.