An annoyance; quick opening of resources no longer possible in command bar

It used to be that you could type the known abbreviation of a book in your library into the command bar to quickly open it.

That is no longer the case, because now "Look Up" and "Layout" are interpreted first before Resources. So you've got to wait until the dropdown appears (which can be several seconds in a large library) and then select the desired title.

This is very irritating, and I think it's poor UI. I request that the behavior be reinstated so that Resource names are interpreted first, at least if it's an abbreviated title that was typed in.

Find more posts tagged with

Comments

Dave Hooton

Logos v7.13 shows Resources then Search.

What is your version of Logos, or are you running Verbum?

Francis

https://community.logos.com/discussion/comment/967212#Comment_967212

Logos v7.13 shows Resources then Search.

Confirmed. Open English Standard Version is the first and default pick when I type ESV.

It would be good if they could likewise prioritise the names of Bible books. When I type Mark, a bunch of selections from guides are proposed first (e.g., open Bible Word Study Guide to markab") and only then is the "Go to Mark" option available.

Rosie Perera

https://community.logos.com/discussion/comment/967212#Comment_967212

Logos v7.13 shows Resources then Search.

What is your version of Logos, or are you running Verbum?

Hmm, it appears I was stuck at v7.9.0.0013 which was RC1. I keep getting updates of resources regularly, and assumed I was getting program updates too. I don't have it set to update automatically, but to let me know when there are updates available, and I generally choose to go ahead and download them. I'm also on the beta channel, so I should be getting the very latest.

It's been a while since I've known how version updating works, and I do seem to recall there was something weird about how you could get stuck on an old version sometimes. I don't remember how.

Anyway, I ran set update channel to default and that only updated me to v7.9.0.0021 (SR-1).

So I ran set update channel to stable and tried update now again. No updates available.

Ran set update channel to beta and update now and it said it was updating, but I'm still on v7.9.0.0021. This is infuriating!

How do I get unstuck? I don't want to uninstall and reinstall.

Reuben Helmuth

https://community.logos.com/discussion/comment/970731#Comment_970731

I'm on 7.14 RC2 and am seeing what you're seeing, Rosie, IF I type a word that occurs in one of my layout names. Typing ESV works for me as you desire, but I don't have ESV in a layout name.

Robert M. Warren

https://community.logos.com/discussion/comment/970731#Comment_970731

Hmm, it appears I was stuck at v7.9.0.0013 which was RC1

Your current version of .NET might be halting you at 7.9. See this thread: https://community.logos.com/forums/t/148412.aspx

DMB

https://community.logos.com/discussion/comment/970782#Comment_970782

Hmm, it appears I was stuck at v7.9.0.0013 which was RC1

Your current version of .NET might be halting you at 7.9. See this thread: https://community.logos.com/forums/t/148412.aspx

This is an interesting problem. I'm at 7.9 too. Over the previous weekend I got a couple Hermeneia volumes at full price. And returned them at full price ... one wouldn't load.

And come this fall, zippo on any upgrades as well. I'd think they'd time their .NET a bit better, but who knows ... maybe MS.

Keep Smiling 4 Jesus :)

That is no longer the case, because now "Look Up" and "Layout" are interpreted first before Resources.

Apologies since unable to replicate using Logos 7.14 RC 2 (Current Stable Release) on macOS 10.13.4 (that includes a layout with ESV in the name):

Anyway, I ran set update channel to default and that only updated me to v7.9.0.0021 (SR-1).

So I ran set update channel to stable and tried update now again. No updates available.

Ran set update channel to beta and update now and it said it was updating, but I'm still on v7.9.0.0021. This is infuriating!

How do I get unstuck? I don't want to uninstall and reinstall.

Curious about Windows version and .NET Framework version ?

Thread reply => https://community.logos.com/forums/p/148412/923742.aspx#923742 includes a Power Shell script.

Keep Smiling [:)]

Rosie Perera

https://community.logos.com/discussion/comment/970976#Comment_970976

Curious about Windows version and .NET Framework version ?

Thread reply => https://community.logos.com/forums/p/148412/923742.aspx#923742 includes a Power Shell script.

Windows 7 SP-1 (technically called "Windows NT 6.1.7601 Service Pack 1," as shown in my Logos.log file.)

I don't think I need to run a Power Shell script, as the info about .NET is also in Logos.log. I'm apparently running .NET 4.0.30319.42000

I was able to update to Logos 7.14 RC2 by manually running LogosSetup from the link in the release notes. But I wonder now whether I'll continue to be stuck and have to update manually going forward, due to having an older version of .NET or whatever.

Rosie Perera

https://community.logos.com/discussion/comment/970747#Comment_970747

I'm on 7.14 RC2 and am seeing what you're seeing, Rosie, IF I type a word that occurs in one of my layout names. Typing ESV works for me as you desire, but I don't have ESV in a layout name.

Glad someone else is able to reproduce this.

Oddly, I'm not seeing it anymore, though. I was able to update to 7.14 RC2 and the problem seems to be gone for me now. I don't think it has anything to do with Layout names, as I'm pretty sure I'd seen the problem before when typing "message" to open The Message, and I have no layouts with "message" in their name.

So that means maybe there's something else at work causing this problem intermittently.

Dave Hooton

https://community.logos.com/discussion/comment/970988#Comment_970988

I was able to update to Logos 7.14 RC2 by manually running LogosSetup from the link in the release notes. But I wonder now whether I'll continue to be stuck and have to update manually going forward, due to having an older version of .NET or whatever.

Setup has installed the required version of .NET in order to install v7.14. .NET 4.0.30319.42000 is misleading as it only states that you are running .Net 4.x as opposed to .NET 3.x (Faithlife acknowledge this but haven't done anything about it). You should now be able to update normally.