BUG: ESV cannot be deselected in multiple resource view
Comments
-
Windows/Mac? Version of Logos?
Does this only happen with ESV as the base i.e. does the fixed ESV occur with another bible as the base?
Dave
===Windows 11 & Android 13
0 -
Yes, right, sorry, completely forgot!
Windows 10
Logos Bible Software 6.9 SR-1 6.9.0.0044 (although the bug wasn't caused by the latest update).
It happens only with ESV as the base.
And, not sure whether it helps, but right now with this configuration (double ESV and UBS5), if I try to switch to any other Bible through "parallel resources", the program crashes.
0 -
-
Added!
0 -
Faithlife need to check this one as panel Preferences for ESV show its Guest Resources as ESV + UBS5! The crash is likely connected with this.
Dave
===Windows 11 & Android 13
0 -
So I have ESV open, and somehow in "multiple resources" mode another ESV got in, which cannot be removed. And what I have is an empty space.
I apologize for your difficulties with this. I'm not certain how things got into this state, but we've made a change that will clear up the problem for you. This fix will be available in an upcoming SR release. Until that ships, I'm not aware of a workaround that will clear up the problem. I am fairly certain that the mentioned crash is directly related.
Andrew Batishko | Logos software developer
0 -
I apologize for your difficulties with this. I'm not certain how things got into this state, but we've made a change that will clear up the problem for you. This fix will be available in an upcoming SR release. Until that ships, I'm not aware of a workaround that will clear up the problem. I am fairly certain that the mentioned crash is directly related.
No problem - this is the first bug I had in 3 years of continual use of the software! I'm simply using another translation for now. And thank you for the exclusive fix for me! [:)]
0 -
This fix will be available in an upcoming SR release.
This build resolves the issue you are encountering, we are not publishing this to the update channel at this time, because there is another bug we are resolving before we do that.
0 -
This fix will be available in an upcoming SR release.
This build resolves the issue you are encountering, we are not publishing this to the update channel at this time, because there is another bug we are resolving before we do that.
Thank you, Angela and FL team, this worked like a charm - the bug is gone!
0
