BUG (SERIOUS) - malformed context menu lookup action
To reproduce - although this is not limited to any example - NRSV to Gen 11:31 - select Context Menu - note the Lookup section which has an unusual layout, unlimited number of entries, and omits the actions that follow look up. I am not happy that I've had to report this a second time. It is the sort of error that should be fixed ASAP because it interferes with a basic program function.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
Comments
This is operating in the way I would expect.
The list of resources for references like these do not use a keylink lookup to find the associated articles as is done with other references. Given the mechanism used, multiple articles per resource are more frequent here. This makes it more important to list the article titles along with the resource. It is arguably a bug that the list does not cap at 5 resources.
There is no Power Lookup option, because Power Lookup doesn't support Biblical Places.
I'm not sure what other actions you are expecting to see.
Andrew Batishko | Logos software developer
It is arguably a bug that the list does not cap at 5 resources.
This is PRECISELY what I was reporting as a bug ... and had reported before.
It's interesting to me that the expectation is that all things would work with Power Lookup.
Interesting to me too as I never intended to say that ... I gave examples of common things I expect to see after the Look up ... I expect to see them because their presence or absence indicate what is possible pursuing this particular piece of data.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
This is PRECISELY what I was reporting as a bug ... and had reported before.
[Y] I'm on board with this as a bug. I'll report it as such on Monday.
Interesting to me too as I never intended to say that
I heard that from Disciple. It wasn't clear to me if that was what you were trying to say. Thanks for clarifying.
Andrew Batishko | Logos software developer
I'm trying to understand the problem more fully.
I see that the Lookup entry is formatted differently but I'm wondering what should appear after it in this case.
The example below just focuses on the word selected and shows a range of functions below the Lookup command. Which of this should be available / make sense for a biblical place / person / sense etc?
Power lookup and Wikipedia are the most common items missing - happens with places, things, and a few others that I've hit.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
The Wikipedia tool doesn't support navigating to a place or thing, or really anything except text, which is why it only shows up on the text-based items like "Selection".
Andrew Batishko | Logos software developer
So you are saying
1) FL can’t enhance the code to reach the text layer so Power Lookup etc can be supported?
or;
2) FL didn’t consider users would have expectations that these functions would be available regardless of what’s happening under the hood, that all users see is text tagged as being a ‘Biblical Place’ or whatever the case maybe and they would naturally expect a Power Lookup could be run on that text?
Either way are you saying the program is behaving as designed and users will just have to change their expectations because there is no case to open? Or are you going to open a case to go back and look if the programmers can meet user expectations on what they see as basic functionality?