Page 1 of 1 (9 items)
This post has 8 Replies | 1 Follower

Posts 102
Andrew Malone | Forum Activity | Posted: Sun, Jan 24 2016 11:59 PM

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?

Posts 28696
Forum MVP
MJ. Smith | Forum Activity | Replied: Mon, Jan 25 2016 12:29 AM

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 Hilarion Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."

Posts 102
Andrew Malone | Forum Activity | Replied: Mon, Jan 25 2016 12:42 AM

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.

Posts 102
Andrew Malone | Forum Activity | Replied: Mon, Jan 25 2016 2:58 AM

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

Posts 22633
Forum MVP
Graham Criddle | Forum Activity | Replied: Mon, Jan 25 2016 3:17 AM

Andrew Malone:

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?

Posts 4264
LogosEmployee
Kevin Byford (Faithlife) | Forum Activity | Replied: Mon, Jan 25 2016 10:36 AM

Andrew Malone:

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.

Posts 8194
LogosEmployee
Bradley Grainger (Faithlife) | Forum Activity | Replied: Mon, Jan 25 2016 12:11 PM

MJ. Smith:
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.

MJ. Smith:
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"... Smile)

Posts 102
Andrew Malone | Forum Activity | Replied: Mon, Jan 25 2016 3:58 PM

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

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

Posts 102
Andrew Malone | Forum Activity | Replied: Thu, Feb 4 2016 2:36 PM

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.

Page 1 of 1 (9 items) | RSS