BUG: Send hyperlinks here not working reliably on Mac (and sometimes on PC)
I've noticed a bug with "Send hyperlinks here". I observed that it only works if/after the target resource tab has been on top in the Logos layout. Otherwise it is ignored, until the target resource is brought on top.
Here is a concrete illustration. I've set the CLASB as "Send hyperlinks here" target. I open a layout where my Bible and the ESVSB are the top tabs :
When I click on the Ezekiel 29:17-30:19 link on the left pane, it is sent to my default Bible and not the CLASB as expected :
Now, I open a layout where the target resource CLASB is the top tab on the right :
When I click on the 2 Kings 25:27-30 link on the left pane, now it is correctly sent to the CLASB as expected :
My conclusion is that for some reason, the Logos software only reads and activates the "Send hyperlinks here" setting if the resource is the top resource in some pane of the layout (it is sufficient that it is brought once to the foreground. After that, it can be put in the background and will be brought back on top when links are sent). As long as the resource remains only in the background, Logos Software will not detect and handle the "Send hyperlinks here" setting correctly.
This issue seems to affect mostly Logos on Mac. Logos on PC generally works, though some times just after Logos startup it does exhibit the same incorrect behavior as well.
Workaround : always save your Logos layout with your "Send hyperlinks here" target resource on top.
Comments
-
This issue seems to affect mostly Logos on Mac. Logos on PC generally works, though some times just after Logos startup it does exhibit the same incorrect behavior as well.
I found your description to be confusing as you appear to be using the same layout throughout, with CLASB being the first tab in the second tile (not pane) in all your screenshots.
So you are saying that the CLASB tab with Send hyperlinks set has to be open/visible for it to function on Mac?
I can't comment on Mac, but Send hyperlinks works on PC even when both books are in the same tile
Dave
===Windows 11 & Android 13
0 -
I've noticed a bug with "Send hyperlinks here". I observed that it only works if/after the target resource tab has been on top in the Logos layout. Otherwise it is ignored, until the target resource is brought on top.
My conclusion is that for some reason, the Logos software only reads and activates the "Send hyperlinks here" setting if the resource is the top resource in some pane of the layout (it is sufficient that it is brought once to the foreground. After that, it can be put in the background and will be brought back on top when links are sent). As long as the resource remains only in the background, Logos Software will not detect and handle the "Send hyperlinks here" setting correctly.
This issue seems to affect mostly Logos on Mac. Logos on PC generally works, though some times just after Logos startup it does exhibit the same incorrect behavior as well.
Workaround : always save your Logos layout with your "Send hyperlinks here" target resource on top.
I can confirm this behavior on Mac. Very annoying [:^)]
Thank you for providing a workaround—definitely a BUG.
0 -
I don't have time to test this on my set up just now Famille, but just to say that the reason that I have not run into this problem myself is because I always keep my 'Send Hyperlinks Here' bible in a floating window.
Pretty much always that window is in a separate space so that I can just flick spaces to see the full reference if the tool tip is insufficient.
tootle pip
Mike
How to get logs and post them. (now tagging post-apocalyptic fiction as current affairs) Latest Logos, MacOS, iOS and iPadOS
0 -
I can't comment on Mac, but Send hyperlinks works on PC even when both books are in the same tile
In my observation (I have both a Mac and PC) it generally works on PC, except right after Logos startup (with the layout immediately loaded at startup). Then, it exhibits the same incorrect behavior as on Mac.
0 -
I can confirm this behavior on Mac. Very annoying
Thank you for providing a workaround—definitely a BUG.
Yes, definitively a bug. [:D]
0