Problem with Proverbs explorer
A problem reported in the thread announcing Proverbs Explorer got lost in other issues
https://community.logos.com/forums/p/122220/799196.aspx#799196
If you look at the second and third post, if you scroll down far enough down in any list in the right panel, the verses stop being rendered and you just get the reference. This was not commented on by Faithlife. This appears to be a bug, is there a comment?
Comments
-
Don Awalt said:
This was not commented on by Faithlife. This appears to be a bug, is there a comment?
I agree it needs a further investigation even though Faithlife were unable to reproduce on Mac.
Dave
===Windows 11 & Android 13
0 -
Don Awalt said:
This was not commented on by Faithlife. This appears to be a bug, is there a comment?
It was commented on later in that thread: https://community.logos.com/forums/p/122220/799714.aspx#799714
0 -
I have tried changing Bibles it uses, scrolling slower/faster, checking other LN topics besides "Wealth", doing it multiple times, it continues to do it. I deleted the log, conducted some attempts, and looked again. There is nothing in the logs indicating a problem. It just doesn't display the text after awhile. (Note if I do it enough times, it does not always stop at Je 17:9 like above, it stops later - but that has only happened twice out of about a dozen attempts.)
What else could I try to find a way to duplicate this? What is this feature dependent upon, to be working correctly?
0 -
Don Awalt said:
I have tried changing Bibles it uses, scrolling slower/faster, checking other LN topics besides "Wealth", doing it multiple times, it continues to do it. I deleted the log, conducted some attempts, and looked again. There is nothing in the logs indicating a problem. It just doesn't display the text after awhile. (Note if I do it enough times, it does not always stop at Je 17:9 like above, it stops later - but that has only happened twice out of about a dozen attempts.)
What else could I try to find a way to duplicate this? What is this feature dependent upon, to be working correctly?
I haven't figured it out either. It's a strange bug...
0
