Anyway to turn off the tooltip?

Comments
-
Hi
I don't know how to turn it off but it looks to be resource-specific. While I get the popup in NAS it doesn't appear in ESV or NRSV.
Graham
0 -
The tooltip will stop if you disable the inline Interlinear. This strikes me as a bug that the NASB would have "extra functionality" when the other Reverse Interlinears behave differently.
Prov. 15:23
0 -
It's time this resource was fixed - it also has a bug with searching Strong's numbers.
Dave
===Windows 11 & Android 13
0 -
I've submitted this request. There is also an open case on duplicate hits for Strong's Number when searching in NASB95.
0 -
Melissa Snyder said:
I've submitted this request. There is also an open case on duplicate hits for Strong's Number when searching in NASB95.
In Logos 3 this is how the KJV and NASB function. Rather than turn it off permanently, why not make it optional?
Ted
Dell, studio XPS 7100, Ram 8GB, 64 - bit Operating System, AMD Phenom(mt) IIX6 1055T Processor 2.80 GHZ
0 -
Ted Hans said:
why not make it optional?
If you have your information tool open and set in the click mode, it will not show anything when you click on any NAS word that produces a popup. Instead it will open the WSNT DICT. The information tool works fine if you have it hover mode. I think it would be handy to have this as an option though, because you have one click access to your lexicons, even if you only have the surface and manuscript on.
"For the kingdom of God does not consist in words but in power"
Wiki Table of Contents
0 -
Ted Hans said:
In Logos 3 this is how the KJV and NASB function. Rather than turn it off permanently, why not make it optional?
Since the popup only appears when the Inline reverse interlinear display is enabled in Logos 4, if there is a change in when the popups appear in the NASB95(still to be determined), you would want to keep Inline display enabled and the Strong's Number line always checked to view them when hovering over a word.
0 -
Melissa Snyder said:Ted Hans said:
In Logos 3 this is how the KJV and NASB function. Rather than turn it off permanently, why not make it optional?
Since the popup only appears when the Inline reverse interlinear display is enabled in Logos 4, if there is a change in when the popups appear in the NASB95(still to be determined), you would want to keep Inline display enabled and the Strong's Number line always checked to view them when hovering over a word.
Yes I would.Thanks
Edit: This is what I wrote on another thread on the same subject, below.
"I am not sure why most on this thread are saying it is a bug. This
function is available in Logos 3 and it seems like a carry over rather
than a bug. It would make sense to make this an optional function for
those who want it and provide a turn off function for the scholars, so
that they can have their day in the sun. Just my opinion - it would seen
to me, all who have contributed to this thread so far have little
difficulty handling the Greek text."Ted
Dell, studio XPS 7100, Ram 8GB, 64 - bit Operating System, AMD Phenom(mt) IIX6 1055T Processor 2.80 GHZ
0 -
Ted Hans said:
"I am not sure why most on this thread are saying it is a bug.
"bug" is an emotive word in this context and Melissa states that this is "still to be determined"; however the Strong's display will still be available from the Interlinear pane as with all other RI's. The real bug is the double-counting of Strong's number results when you perform a Search.
Dave
===Windows 11 & Android 13
0 -
Thanks everyone for all the suggestions, I can click on the word for now so that this tooltip won't shows up. Although I really would love to see an option to turn it on/off and if that is possible, apply to every scenarios, that sounds easier to me, [;)]
0 -
Has there been any progress in fixing this bug? There should be a button in the top user interface to quickly switch the tooltips off and on.
Gold package, and original language material and ancient text material, SIL and UBS books, discourse Hebrew OT and Greek NT. PC with Windows 11
0 -
Veli Voipio said:
Has there been any progress in fixing this bug?
Yes, it was fixed two years ago in 4.1: http://community.logos.com/forums/p/21722/167298.aspx#167298
0