Bug: 4.3 Beta 7: PBB: Hover over link yields duplicate popup

Create a link using the following syntax:

[[Bible:Ge 25:8]]

Compile the PBB and then hover over that link in the resulting book. The popup is duplicated.

Here's the source document in Word:

Here's the resulting book, with mouse hovering over that link:

Notice the popup has the link duplicated.

A question while I'm at it: how come no popup preview of the Bible text at that location comes up in a PBB Cross-Reference Index? It works in the New Treasury of Scripture Knowledge. Do I need to put some sort of tag in to get this to work? Is it even supported? Or is this a bug?

Find more posts tagged with

Comments

Mark Barnes

The second problem is caused by a bug which creates both an internal resource link and a datatype link. The lack of a popup is a side-effect of this bug. It's documented in the Wiki as:

The compiler does not handle datatype links correctly (see below for
terminology). When specifying a datatype link, the compiler creates both a datatype link to any resource, and
an ordinary link to the current resource. This is correct only if the
current resource has a location that matches the datatype. If it does
not have that location, the compiler should not add the ordinary link
because doing so prevents the datatype link working. The work around is
that instead of clicking on the link, you can right-click on it, select
the datatype and choose ‘open’.

It's likely the first problem is caused by the same bug, although possibly that only happens when certain document types are used, or when documents have Bible milestones.

As a side note, really your tags are incorrect based on what I think you're trying to achieve. That's probably not helping:

[[Bible:Ge 25:8]] should read [[Ge 25:8|Bible: Gen 25:8]]

Rosie Perera

As a side note, really your tags are incorrect based on what I think you're trying to achieve. That's probably not helping:

[[Bible:Ge 25:8]] should read [[Ge 25:8|Bible: Gen 25:8]]

I thought, based on my reading of the wiki page, that the label was optional and only required when the text you want to display is different from the link. So if I'd wanted it to read "v. 8" for example, in a passage where I was talking about Genesis 25, I'd need to put in the label. Are you now telling me that the label is required all the time? If so, then the wiki page is misleading.

Mark Barnes

I thought, based on my reading of the wiki page, that the label was optional and only required when the text you want to display is different from the link. So if I'd wanted it to read "v. 8" for example, in a passage where I was talking about Genesis 25, I'd need to put in the label. Are you now telling me that the label is required all the time? If so, then the wiki page is misleading.

No, but:

based on the screenshots above, your input text was Ge 25:8, but your output text was Gen 25:8 hence my assumption of you needing a label.
If you just want the text to remain the same, you don't need a tag anyway. It should just be automatically interpreted.

Rosie Perera

based on the screenshots above, your input text was Ge 25:8, but your output text was Gen 25:8 hence my assumption of you needing a label.

That was Logos's fault. I would have been happy with Ge 25:8 as the output text, but it converted it to Gen 25:8. I was happy with that too, so I left it without a label. I wouldn't want to put in what I'd consider to be unnecessary redundancy. It makes more work for me.