4.5a: BUG: Problems with Text Comparison selecting a collection of BiblesClosed
Two problems here.
First is a bug I'm pretty sure: the full title of a collection of Bibles that I have does not match in the dropdown list in Text Comparison (see screencast for a demonstration of this).
Second is a UI weirdness or design flaw. It seems you cannot get the item you type into the Resources box in the Text Comparison tool to "take" unless you click the blue arrow icon. Hitting Enter should be equivalent to clicking the blue arrow icon, but I try it repeatedly in the video below, and it doesn't do anything. At one point in the video, I see the focus highlight around the A icon for Show Differences, which would explain in that instance why Enter does nothing, but it does nothing even when the insertion point is clearly sitting there after whatever I'd typed in the Resources box.
Here's the screencast:
Comments Closed
It may be a bug. but from what I have done in the past I have always had to hit 'enter' twice, especially when choosing a different collection. It seems to go back to highlight the text, as if I want to change it. Also, when I type in a different set by choosing them, I still have to hit 'enter' twice and then again on the selected text. I always thought that was the 'how' in L4, never had to do this in L3.....whoda thunk it....
DISCLAIMER: What you do on YOUR computer is your doing.
Hitting Enter should be equivalent to clicking the blue arrow icon, but I try it repeatedly in the video below, and it doesn't do anything.I agree this is a problem. If it's by design, then it's a most confusing design.
Concur user interface design is confusing; seems Logos 4 on Mac and PC needs a keystroke (enter or tab) for confirmation.
Choosing or changing resource list for Text Comparison is a bit tricky: click item from drop down list, then press enter to confirm click, followed by blue arrow to compare text.
Seems Logos 4 has some confirmation checks (i.e. "Are you sure ?") that lack user visibility, which can be a bit perplexing to use.
Another example is editing a highlighting style name using Logos 4.5b SR-1 on Mac OS X, which needs a tab key to be pressed so can click save to keep name change (if forget to tab and click save, name edit is discarded). On Windows 7, can edit style name, then click save.
Keep Smiling [:)]
I'm going to give this another try, as I realize my previous answer was pretty unspecific. This is with regard to the second issue, not the first (the first has already been logged as a bug).
What I meant by "by design" is that you do have to hit "enter" twice in order to get to a resource, if the resource title has more than one possible match.
For example, if I type in "ESV", I have to hit "enter" twice because I have more than one possible title with "ESV" in it. The first "enter" selects/confirms "ESV" as my title, and the second "enter" runs the text comparison.
If I have a completely unambiguous title, such as the detailed full name of a collection that has no text matches with other titles, then I can type the full name and press enter once, and the text comparison is run. Another example is "NIV84": as my collection has no other titles containing that text, it is an exact match and I can press enter once and have it run the text comparison.
As to the discrepancy between the docked panel and the floating window, I was unable to reproduce that in build 4.5b SR-1. Are you still seeing this?
As to the discrepancy between the docked panel and the floating window, I was unable to reproduce that in build 4.5b SR-1. Are you still seeing this?I was never witness to that discrepancy. Perhaps Dave Hooton could say whether he's still seeing it.
It now behaves as described for an entry like NIV with a choice of bibles to be made - confirming with a click on the arrow icon (4.5c beta) or a second "return". It's fiddly, sometime requiring a third return.
Dave
===
Windows 11 & Android 13
I can partially reproduce (with ESV, NIV) in a panel, where you have to enter twice. But it is OK in a floating window.
Dave
===
Windows 11 & Android 13
Yup, I had noticed the latter before on another occasion but forgot to note the exception. Thanks for pointing that out.