BUG: Clicking Marginal Link Opens LXX Interlinear Instead of Linking to Opened Bible Text???? WHY!!!

As pic shows, I was interested in looking at the Tanakh: reference for Gal. 3:10, which is Deut. 27:26. For almost 25 years of my life, clicking that link would take me straight to...wait for it!...Deut. 27:26 in my opened NASB95. But just now, for no perceptual reason, this cursed program decided to do something else...

...instead of my NASB95, it decided to take me to this...

My cursor is still in the exact same spot as where I clicked the link. How does CRAZY crap like this just happen out of the blue?? And then, in the process of attempting to figure out this travesty's cause, THIS happens. Unbearable.

Find more posts tagged with

Desktop App

Comments

MJ. Smith

What are the priorities of the Bibles in question? Clicking on a link has always taken me to my highest priority Bible containing the reference.

David Paul

What are the priorities of the Bibles in question? Clicking on a link has always taken me to my highest priority Bible containing the reference.

I have NASB95 at the top, and it is also the Bible which I am in. Of course, on one level, why would that matter...I have made no changes at all to any of my settings.

Btw, this condition is apparently now the default. Every chapter/verse link I click is taking me to the aforementioned (if pics count) LXX. Infuriating. [:@]

MJ. Smith

Btw, this condition is apparently now the default.

For me, the default is still my top Bible.

Go to your library and move the LXX down in priority and the problem will resolve. If it isn't obviously the top priority check the advanced prioritization for the NASB95.

David Paul

Actually, I don't think that version of the LXX (Swete) is even in my priorities list. I have another LXX at about 15th place, but when Swete was released, I closed the other LXX and opened Swete in my Bibles window. I never even bothered to amend the list. NASB95 is still atop the list, so if it were a "natural" priorities issue, then it really shouldn't be an issue. And Swete isn't even included, so it shouldn't even be capable of receiving priority.

MJ. Smith

Can you please show screen shots of your priority list? What you are describing has not been replicated by others and is exactly the behavior expected from prioritization as illustrated by my screen shot. I can think of another possibility, but I'll not set up a test for it until I am certain your priorities are not to blame.