REQUEST: Double-clicking to look up primary Hebrew word - not suffix
Double-clicking compound Hebrew words, like וַתִּרְצֵֽנִי (the last word in Genesis 33:10, for example) opens up the lexicon entry for אֲנִי which is such a common word it’s not likely to be what people are wanting to look up. Rather, double-clicking should open the lexicon entry for verb stem רָצָה. Sure, I can get there by right-clicking on the word, waiting for the popup window to populate, clicking on the appropriate lemma and then selecting 'lookup'. But changing the default to not look up suffixes or prefixes (such as וַ, for example) but instead looking up the primary lemma would be useful and would speed up work.
Even better, adding a popup (from the highest-priority Hebrew or Greek lexicon) that appears when hovering over a Hebrew (or Greek) word (similar to what appears when hovering over a hyperlink to another word in a lexicon) would make life faster too.
Comments
-
When I double-click on וַתִּרְצֵֽנִי, in either the AFAT or BHS/WHM 4.2, it opens the lexicon to I רצה. This may be due to the later build on my system, but it may help to know what resource you're double-clicking in and what lexicon is opened.
0 -
Melissa Snyder said:
When I double-click on וַתִּרְצֵֽנִי, in either the AFAT or BHS/WHM 4.2, it opens the lexicon to I רצה. This may be due to the later build on my system, but it may help to know what resource you're double-clicking in and what lexicon is opened.
Does it matter which part of the word contains the cursor when you double-click?
EDIT: Answered my own question. No matter where I double-click in a word, BDB opens to the main word.
0 -
I don't have BHS+WHM, I have BHS+WIVU morphology - not sure if that makes a difference. When I double-click the lexicon that opens by default (my choice) is the Enhanced Brown-Driver-Briggs Hebrew and English Lexicon. And, no, it doesn't make any difference which part of the word I double-click on.
0 -
Stuart Robertson said:
I don't have BHS+WHM, I have BHS+WIVU morphology - not sure if that makes a difference. When I double-click the lexicon that opens by default (my choice) is the Enhanced Brown-Driver-Briggs Hebrew and English Lexicon. And, no, it doesn't make any difference which part of the word I double-click on.
I just tried it in the BHS/WIVU with the BDB as my default and it is also opening to the main word. Since this is also working correctly for Jack, can you confirm that you have 4.2a Beta 3 installed?
0 -
Yes, I have 4.2a beta 3... here's the string from the about box:
Logos Bible Software 4.2a Beta 3 (4.21.4.8572) (Update Channel: beta)
I'm running on Snow Leopard 10.6.5, Macbook Pro, etc.
For simple (non-compound) words the correct lexicon entry opens upon double-click, but any compound words always open the lexicon entry for the suffix. For example, still in Genesis 33:11, double-clicking on חַנַּ֥נִי (in the phrase כִּֽי־חַנַּ֥נִי near the middle of the verse) opens the lexicon at אֲנִי instead of at חָנַן. If need be I can create another screencast "video" to show this, though I'd rather have Logos take my word for it and forego the time needed to create a screencast.
Not sure if it matters, but I have BDB in one floating panel (along with various other lexicons arranged in tabs), with ESV and BHS alongside each other in the "main" Logos window.
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 20.0px 'SBL Hebrew'}
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 20.0px 'SBL Hebrew'}
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 20.0px 'SBL Hebrew'}
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 20.0px 'SBL Hebrew'}
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 20.0px 'SBL Hebrew'}0 -
I just realized that I posted to the Windows (PC Beta) forum instead of to the Mac Beta forum... can you try this on Logos for Mac - that's where I'm seeing the issue. I just checked the Windows version in Parallels and the Windows version works correctly - it's the Mac version that has the problem.
0 -
Also, I've just noticed how "snappy" the Windows version feels compared to the current Mac version... although things have improved a bit in the latest Mac beta it feels very sluggish, generally speaking, compared to the latest Windows beta - and that's with the latest Windows beta running inside a virtual machine (Parallels 5)... Here's hoping some of that "optimization magic dust" will be sprinkled on the Mac version too.
0 -
Stuart Robertson said:
I just realized that I posted to the Windows (PC Beta) forum instead of to the Mac Beta forum...
I should have remembered that you are a Mac user. [:$]
Stuart Robertson said:can you try this on Logos for Mac
Unfortunately, since the resource update the other day, I cannot get the Mac version to run (I have reported that in another thread). Today's resource update made things even worse.
0 -
Stuart Robertson said:
I just realized that I posted to the Windows (PC Beta) forum instead of to the Mac Beta forum... can you try this on Logos for Mac - that's where I'm seeing the issue. I just checked the Windows version in Parallels and the Windows version works correctly - it's the Mac version that has the problem.
I should have realized your main system was a Mac, too. I just tried the same steps in Mac version and I'm getting the same results as you. I'll submit the report to development. Thanks.
Update: This will be fixed in the next Mac Beta. (I'll move this thread to that forum.)
0 -
0
