passage location problems?

Andrew Malone
Andrew Malone Member Posts: 121
edited November 21 in English Forum

Perhaps it's just me. And perhaps there's an older thread on this; please redirect me. Smile

I'm sure older versions of the iOS app were pretty robust when it came to manually typing the passage I wanted to jump to. I could offer 'Rev' or 'Rev4' or 'Rev7.9', and they'd all work (though, of course, taking me to different places).

At the moment (v5.0.4), I can't get the middle syntax working: book+chapter. Although it works with rare combinations (e.g. 'Gen2'), I generally can't get anywhere with this. I can get 'Matt' or 'Matt15.24' but not 'Matt7'. By extension, 'Matt7.1' does work, but it's frustrating to add.

I'd peg it as some kind of server issue. Everything runs fine (though a little slower) when I'm connected to wifi. But I'm often offline, as when in church or class, and that's when the functionality differs.

Any suggestions?

Tagged:

Comments

  • MJ. Smith
    MJ. Smith MVP Posts: 53,121

    I know nothing about iPad's ... but the references that you typed in the post would generally be invalid in Logos on the desktop. A colon is used between chapter and verse i.e. American not European tradition; and a space is expected between the book and the chapter.

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Andrew Malone
    Andrew Malone Member Posts: 121

    Thanks, MJ. But one of the things that I like about the desktop version – unlike other programs I've used in the past – is that Logos is quite robust. Bible books recognise a number of abbreviations (Ex, Exod, Exodus); chapter and verse can be separated by colon or full-stop/period or even a space; and it doesn't matter whether there's a gap or not between the book and any following reference. It recognises everything from 'John 3:16' through to 'jn3 16'.

    The older iOS version used to be equally robust, but not the newer one.

  • Andrew Malone
    Andrew Malone Member Posts: 121

    Admittedly, I'm still enjoying that robustness with Logos 4. Has that changed with newer desktop versions? [*-)]

  • Graham Criddle
    Graham Criddle MVP Posts: 32,470

    Admittedly, I'm still enjoying that robustness with Logos 4. Has that changed with newer desktop versions? Confused

    No - "Matt7" takes you to Matthew 7.

    Any particular reason why you haven't upgraded to Logos 6?

  • Kevin Byford (Faithlife)
    Kevin Byford (Faithlife) Member, Logos Employee Posts: 4,309

    But I'm often offline, as when in church or class, and that's when the functionality differs.

    Any suggestions?

    We're taking a look at this issue.

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,958

    but the references that you typed in the post would generally be invalid in Logos on the desktop

    They are not. All the example references ('Rev' or 'Rev4' or 'Rev7.9') work fine in the desktop software. (We don't force you to type a colon when a period is much more convenient.)

    Completely hijacking this thread, but here's another tip: If you're already in Revelation 7:9, simply type "1" to go to Rev 7:1, or "8.1" to jump to Rev 8:1.

    A colon is used between chapter and verse i.e. American not European tradition; and a space is expected between the book and the chapter.

    The software can figure this out. (Don't get me started on online ordering forms that insist on "enter your credit card number WITHOUT DASHES OR SPACES"... [:)])

  • Andrew Malone
    Andrew Malone Member Posts: 121

    Oooh. I love the new tip! Jumping to nearest relevant proximity is extremely useful.

    Will look forward to the results of Kevin's investigations...

  • Andrew Malone
    Andrew Malone Member Posts: 121

    How delightful to see the latest app update (5.1.1.) promising "better offline navigation support" (and Kevin's post with release notes even references our current thread). All the examples I listed above do seem to be working properly now. Thanks to all involved.