BUG: DBL issue with links to Strong's and TWOT?
I just started using A Dictionary of Biblical Languages w/ Semantic Domains: Hebrew (OT).
When I hover over a Str or TWOT number (such as TWOT Number 1631a), I thought the program would show that entry from the TWOT. Instead it shows the text of the DBL entry it's linked from.
FYI, the Louw Nida links do work properly and show the specified LN entry. This issue only seems to affect Strong's and TWOT links.
This is from 7.7 SR-1 (7.7.0.0018) on macOS 10.12.5 (16F73).
LLS:46.30.10
2014-12-16T21:21:01Z
DBLHEBR.logos4
LLS:46.50.3
2016-07-07T18:18:52Z
TWOT.logos4
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
Comments
-
This sounds like a prioritization issue. Since DBL is tagged to Strongs and to TWOT, it will come up if it is prioritized higher than other lexicons tagged to those same datasets. If you want TWOT or ESL to come up, prioritize them higher than DBL.
Have joy in the Lord!
0 -
I do have DBL prioritized first for lexicons (because I wanted it to be used for other lookups). I didn't realize it would also affect lookups within the DBL.
FYI, I don't have ESL or TWOT prioritized, but do have LN prioritized.
I'm confused that a link which I expected to specifically refer to TWOT would show me a prioritized entry from DBL instead of the specific entry from TWOT. Please forgive the newbie question, but is that expected behavior for lexicon links to other lexicon entries? I can understand prioritization regarding bible references or meanings of Hebrew words being from a preferred translation or lexicon, but in this case, aren't we talking about a resource link, not a word lookup? Needing to change priorities just to preview a link to a specific lexicon entry seems... tedious.
Also, LN numbers behave differently, even though LN is prioritized lower than DBL. Is there a different reason why the DBL displays LN entries when I hover over LN numbers?
As an aside, if this isn't a bug, isn't the hover footer (in the original post) that says the text is from the TWOT incorrect, if the hover text was not intended to be from the TWOT?
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0 -
PetahChristian said:
I do have DBL prioritized first for lexicons (because I wanted it to be used for other lookups). I didn't realize it would also affect lookups within the DBL.
You can use advanced prioritization to have links from inside DBL open TWOT/ESL
Have joy in the Lord!
0 -
NB.Mick said:
You can use advanced prioritization to have links from inside DBL open TWOT/ESL
Thanks for the advice.
I tried this, but it only seems to fix one of the two sets of resource links, not every resource link. For example, advanced prioritization lets me now hover over TWOT numbers and see the TWOT entry for that number, but ESL numbers still show the DBL text.
Also advanced prioritization introduces a more serious problem for me. Now when I click to see information on a Hebrew word, it uses BDB (#2) instead of DBL (#1) because of the "Apply only to" prioritization.
I do appreciate the help, but can't understand why
- this is a prioritization issue, or needs prioritization workarounds to achieve a particular behavior. Shouldn't a Strong's number link show the corresponding ESL entry and a TWOT number link show the TWOT entry, like the LN number currently does now?
- Why do ESL and TWOT numbers behave differently than LN numbers?
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0 -
PetahChristian said:
- this is a prioritization issue, or needs prioritization workarounds to achieve a particular behavior. Shouldn't a Strong's number link show the corresponding ESL entry and a TWOT number link show the TWOT entry, like the LN number currently does no
You will not see the behavior you are expecting because these are not coded as links to resources. They are coded as links to data types and the way you set up your prioritisations will determine what resource will show in the popup if you hover over the datatype link (or open if you click on it.
PetahChristian said:2. Why do ESL and TWOT numbers behave differently than LN numbers?
They do not behave any differently in reality, it is only your assumption that theses are links to resources, rather than datatypesc that leads you to think they are behaving differently. Hence the answer to this question is the same as the answer to the previous question, all of these links are not hard coded to resources but to datatypes.
The power user will appreciate this flexibility, the beginner will find it problematic.
0 -
I can appreciate that MultiView can display entries from several lexicons. I do use that features for bibles/commentaries, but found that it's not as readable with too many lexicons open side-by-side -- its columns become too narrow.
I'm aware that Power Lookup can display snippets from many lexicons at once, but I'd like to glance at more than a couple of sentences.
I also understand that I can right-click to lookup entries from a specific lexicon in another tab.
I happen to like the hover popup. It's quick, readable, doesn't take up any screen space, and doesn't involve any extra steps to dismiss it.
Disciple of Christ (doc) said:The power user will appreciate this flexibility
Perhaps KS4J will pop in with an illustration educating me on how to best use that flexibility, as I'm still left in the dark as to how to simply preview (hover) to see what the ESL or TWOT says, without having to keep multiple lexicons/tabs open at once.
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0 -
PetahChristian said:
Perhaps KS4J will pop in with an illustration educating me on how to best use that flexibility, as I'm still left in the dark as to how to simply preview (hover) to see what the ESL or TWOT says, without having to keep multiple lexicons/tabs open at once.
I am sorry I was on my phone earlier and so couldn't do any screen shots. I hope below helps you visualize this a little bit more.
(Note: I dont' have ESL on my system, I choose to hide it and my personal preference for Strong's Hebrew Numbers is to look at Complete Word Study Dictionary: Old Testament.(WSDOT) So in my screen shots below preened WSDOT is ESL to help translate the examples to what you want to achieve with your prioritizations Petah.
Advanced prioritizations can be a little bit off putting and hard to setup. The easiest way to check how you have them set up is as follow.
1) In DBL right click on the strong's number
2) Select Strong's Hebrew # from left hand side of menu
3) review prioritization order on left hand side
In my library this looks like:
Avoiding unexpected behavior.
The above order is the way I want my resources to be prioritized, so when I hover over a Strong's hebrew # link I want to see the information from the Complete Word Study Dictionary: Old Testament if the Strong's Hebrew number is found its index. If it's not found it will show informaiton form the first highest prioritized resource on the list that does have that Strong's Hebrew number in its index.
But lets say before these five resources I had a general entry from DBL Hebrew as higher priority as follows:
In this scenario the prioritization entry for DBL will override the advanced prioritization settings below it and when I hover over or click on a Strong'[s Hebrew # hyperlink DBL will now be used by Logos as its first choice, rather than the Complete Word Study Dictionary: Old Testament.
To avoid this I would need to change my prioritization order to look one of the following examples. Note each of these examples will impact slightly different only the order in which other data types behave and so there is not one right way, the key is to ensure that DBL is either below the advanced strong's hebrew # number prioritization for Complete Word Study Dictionary OT or if it is above this resouce it must be setup as an advanced prioritization for another data type:
0 -
Disciple of Christ (doc) said:
when I hover over a Strong's hebrew # link I want to see the information from
Aha, I understand the flexibility now! Many lexicons have entries for a Hebrew Strong's Number, and we're not limited to only seeing what ESL says about a particular number.
The examples are very helpful! I've been able to setup the advanced prioritization and can now hover over each of the numbers in the DBL to see entries from specific lexicons.
Thanks very much!
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0
