L/V 10 Tip of the Day #56 Dictionary used on double-click when set to Look up

MJ. Smith
MJ. Smith Member, MVP Posts: 53,041 ✭✭✭✭✭
edited November 21 in English Forum

Another tip of the day (TOTD) series for Logos/Verbum 10. They will be short and often drawn from forum posts. Feel free to ask questions and/or suggest forum posts you'd like to see included. Adding comments about the behavior on mobile and web apps would be appreciated by your fellow forumites. A search for "L/V 10 Tip of the Day site:community.logos.com" on Google should bring the tips up as should this Reading List within the application.

This tip is inspired the forum post: All the people in the bible - Logos Forums

Note: this post assumes that in Program Settings, "Double-Click Action" is set to "Look up". If it is set to Search, Search inline, or Select word this post does not directly apply.

When you double-click on a word, the highest priority resource indexed by headwords that contains the word will be opened and positioned on the word.  For purposes of illustration, I have put Losch, Richard R. All the People in the Bible: An A–Z Guide to the Saints, Scoundrels, and Other Characters in Scripture. Grand Rapids, MI; Cambridge, U.K.: William B. Eerdmans Publishing Company, 2008. at the top of my priority list.

So when I double-click on Isaiah All the People in the Bible is the resourced opened.

If I remove that forced priority, I (deliberately) get an unexpected result:

Why? Because this study Bible contains a Glossary that is indexed by English headword, so even though the resource is not encyclopedia, the index causes it to be searched in the lookup.

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."

Tagged:

Comments

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,672 ✭✭✭

    If I remove that forced priority, I (deliberately) get an unexpected result:

    Why? Because this study Bible contains a Glossary that is indexed by English headword, so even though the resource is not encyclopedia, the index causes it to be searched in the lookup

    Use Advanced Prioritization to restrict that book to the Bible datatype (and prioritize it with your Study Bibles/Commentaries).

    The same problem can arise with the NLT unless restricted to Bible.

    Dave
    ===

    Windows 11 & Android 13