Hyperlinks Broken in Note Files
In Logos 5, hovering over a verse reference or hyperlink to another resource in a NOTE FILE caused the data to be displayed in a pop-up window. However, in Logos 6 such is NOT the case. The pointer does change appropriately but the hyperlink does NOT display associated data and can only be accessed by using CMD-CLICK.
I have checked this anomaly in hyperlinks in Bibles and other resources (commentaries and encyclopedias) and hyperlinking does work properly.
I believe ths anomaly only occurs in Note Files.
Thanks for the release of SR-1 ... hopefully this issue will be fixed in SR-2 and released ASAP.
Matt
Comments
-
-
Hi Matt
Is this what you mean?
If so it is working fine on my iMac OS 10.10 and Logos 6 SR1
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 -
Mike Binks said:
Hi Matt
Is this what you mean?
If so it is working fine on my iMac OS 10.10 and Logos 6 SR1
I think he might be talking about scripture references actually typed in the body of a note. Does that work for you as well?
0 -
Fredc said:
I think he might be talking about scripture references actually typed in the body of a note. Does that work for you as well?
Hi Fred
You're right! They don't! (work that is)
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 -
Mike Binks said:Fredc said:
I think he might be talking about scripture references actually typed in the body of a note. Does that work for you as well?
Hi Fred
You're right! They don't! (work that is)
Seems like it must be a Mac bug then.
0 -
We are actively looking into this bug. It does appear to only affect Mac (and even there we have several mac users that are not affected). We will update this thread as progress is made.
0 -
We have tracked down this issue and it will be fixed in an upcoming release.
Mac Developer
Faithlife0 -
Martin Potter said:
We have tracked down this issue and it will be fixed in an upcoming release.
This should be fixed in 6.0 SR-3.
0
