BUG: Cmd-F doesn't work very well in the Catholic Lectionary
I hit Cmd-F, type a word and, if necessary, hit Enter. I get to
Only the word isn't there. It's an inch or two above:
Mac Pro (late 2013) OS 12.6.2
Comments
-
Unfortunately, it's even worse than above:
2) The search result only shows up at all if I'm already under the right date. Otherwise the 'Find' feature behaves as if there's nothing to find. I noticed this yesterday as well, but I had such a large swap file at the time that I wanted to make sure before reporting it that it was a real issue, and not just caused by it taking so long that I gave up too early.
I presume this is another one of those issues that occur because the lectionary isn't a 'real' resource, but a kind of 'reading plan' fetching the actual text from somewhere else? What makes this one so tricky, though, is that you believe you've done a search and found nothing, but in reality you haven't actually done the search at all. And there's no way of knowing that.
3) I don't yet know if this is a repeatable bug or just a one time thing, but this morning when I opened my lectionary layout, the lectionary tab opened to where I last was (i e the passage in the OP), instead of to this mornings reading, where it was when I saved the layout. And, no, I can't possibly have forgotten to save, as the other tabs were in the right place.
Haven't managed to repeat it so far, though.
Mac Pro (late 2013) OS 12.6.2
0 -
OK, now I've tested this in the Daf Yomi as well and found that it is a resource type issue, not a resource issue, and a very weird one at that, so let me rephrase things:
1) If the wanted word is found, the lectionary opens to the empty space below the text it's in -- which in the case of the Daf Yomi can be a very long way from where it actually is.
2)
- I chose an unusual word that occurs in the Gospel for both the Thursday of the 19th Week and St Stephen (same date, same Gospel) and typed it into the find box.
- I scrolled to and put the focus in the first OT reading for St Stephen, and started the search. Except for issue 1) it found the word in the NT reading for the same day.
- I then moved back to the OT reading for the Thursday, started the search again, and it found the word in the NT reading for that day.
- I went on to the Assumption, did the same thing, and again it found the word in the Thursday reading.
- I did the same thing for the Assumption Vigil and St M M Kolbe. Same result.
- Then I jumped a few days back to St Clare -- and suddenly Logos can't find the word anymore.
- Same thing if I change direction and try to go forward again. Suddenly it can't find the word from a position it easily found it from minutes earlier.
As long as I move backwards one step at the time Logos keeps finding the word, but as soon as I move direction or jump a day it's as if the word doesn't exist in the resource. I really hate the kind of bugs that makes you think you've performed a full and accurate search when you haven't!
But at least the fact that it can find things across text and date boundaries under some conditions ought to mean that it's a 'real' bug, and not something that can't possibly be fixed until the whole lectionary 'feature' is revamped.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
1) If the wanted word is found, the lectionary opens to the empty space below the text it's in -- which in the case of the Daf Yomi can be a very long way from where it actually is.
I was able to reproduce this and have created a case for development.
fgh said:As long as I move backwards one step at the time Logos keeps finding the word, but as soon as I move direction or jump a day it's as if the word doesn't exist in the resource.
I am unable to follow the steps on this. If this is still an issue, could you provide a specific search word and location for me to reproduce? I understand you're not finding words that are clearly there - but I'm having trouble following the mechanics of it.
0 -
Dylan Rondeau said:
I was able to reproduce this and have created a case for development.
Thanks.
Dylan Rondeau said:I am unable to follow the steps on this. If this is still an issue, could you provide a specific search word and location for me to reproduce?
And I who thought I was pretty detailed above.[:)] But, OK, here are some even more detailed steps:
1) Prioritize Bibel 82.
2) Open the Catholic Lectionary.
3) Open the TOC.
4) Expand the 2011-2012 section, then the last Ordinary Time section, then both the Saint Dominic and Saint Maximilian sections (like in the screenshot above).
5) Click on Saint Stephen of Hungary.
6) Scroll down to the Gospel and copy the word 'bödelsdrängarna' in v 34.
7) Scroll up so that the top of the screen is somewhere in the OT reading, and click in it to make sure it has focus.
8) Cmd-F + Cmf-V (+ Enter, if necessary).
>> The resource 'jumps', and if you scroll up a little, you will see that -- except for bug 1's interference -- the word was found as it should.
9) Click one entry above in the TOC, i e Thursday of the Nineteenth Week (which, in this particular year, was actually the same date, with the same texts).
10) Scroll down to the OT, click for focus, and then click the down arrow beside the find box.
>> Scrolling up a bit, you will again find that the word was found (but this time in the Thursday Gospel, as that's closer to the starting point).
11) Click another step above -- i e Assumption (Day) -- scroll down to the OT, click for focus, click the down arrow, and scroll up a little.
>> Again the word is found.
12) Click yet another step above -- i e Assumption (Vigil) -- scroll down to the OT, click for focus, click the down arrow, and scroll up a little.
>> Again the word is found.
13) Now jump several steps backwards and click on Saint Claire, scroll down to the OT, click for focus, and click the down arrow.
>> This time nothing at all happens. The resource doesn't move. At most you may get a [completely false] pink Find Box, claiming the word doesn't exist in that direction, but most of the time I haven't even gotten that.
As long as one starts the search in a day where the word exists, and then goes backwards one TOC entry at a time, Find keeps finding the word, but if one does one of the following, it generally doesn't:
- jumps several steps backwards, especially over a 'section border'.
- turns around and starts going forward instead.
- forgets to click for focus, and tries to do that after having clicked the down arrow.
- clicks the wrong entry in the TOC, and then immediately the right.
- just opens the Lectionary to a random location and tries to search for a random word that doesn't happen to be in that day's texts.
IOW, Find only works if I already know where the results are...
Mac Pro (late 2013) OS 12.6.2
0 -
Bump.
Mac Pro (late 2013) OS 12.6.2
0 -
Bump again.
Mac Pro (late 2013) OS 12.6.2
0 -
Sorry it's taken so long for me to get back to this. I was still very new when I last responded to this, and I'll admit a lot of this went over my head and it dropped off my radar.
I am able to reproduce the issue, and I'll make a case for it.
fgh said:I presume this is another one of those issues that occur because the lectionary isn't a 'real' resource, but a kind of 'reading plan' fetching the actual text from somewhere else?
This is what I suspect as well.
0 -
Dylan Rondeau said:
I am able to reproduce the issue, and I'll make a case for it.
Talking with the devs on this, the amount of resources required to fix this for dynamic text (lectionaries) is disproportionate to the ease of working around it. Since the lectionary includes links to the actual resource, the best way around finding a specific word is to open the resource and use Find there.
We may come around to this in the future, but currently it is not a priority.
0
