BUG: Text Comparison unusable

I opened the Text Comparison Tool and clicked on the Bible list to test a different selection of texts. The text selection box did not open. Instead I got this:

Running

Verbum 10.1
10.1.0.0039

Closed and reopened the tool to get:

Killed program to get logs:

6866.nov18logs.zip

I suspect this is an ungraceful handling of the small library in this installation, specifically when a specified resource is in the cloud. The full installation is working.

Find more posts tagged with

Comments

Jack Caviness

Logos 10.1 Mac OS 13.0.1

Worked correctly for me. Perhaps a Verbum or Windows bug?

GregW

**EDIT: Apologies - I just noticed this was the Beta forum - sorry!**

I just tried it on Windows 11, Logos 10.0 SR2 and it worked fine as below:

Savanna Lineberger

Hi MJ,

Thanks for reporting this, I will take a look into this.

Matt Mattox

Hello MJ,

Are you still running into this? I too, was not able to replicate and was able to load the text selection box.

MJ. Smith

https://community.logos.com/discussion/comment/1238148#Comment_1238148

Yes, whenever the first resource to be compared (the base) is not on the device.

If the passage does not occur in the first resource when the resource is on the device, the error is handled correctly.

Matt Mattox

https://community.logos.com/discussion/comment/1238153#Comment_1238153

I'm not sure I am totally following. Can you provide some repro steps in a list format so I can follow along and get into your state?

Example -->

1. Do this

2. Then do this.

etc.

MJ. Smith

https://community.logos.com/discussion/comment/1238154#Comment_1238154

Take an existing list of versions to compare
Go to the library and remove the first version from the device
Return to compare text and try to run the unchanged list of version to compare

No, one would never do this deliberately except to recreate the problem. It happens because the lists of resources for the text comparison are synched across multiple installations. When one installation is stripped to minimum resources, this condition occurs with some frequency.

Matt Mattox

https://community.logos.com/discussion/comment/1238156#Comment_1238156

>No, one would never do this deliberately except to recreate the problem. It happens because the lists of resources for the text comparison are synched across multiple installations. When one installation is stripped to minimum resources, this condition occurs with some frequency.

This is good to know, thanks. We can put this in the backlog then and look at it more if the issue comes more severe.

Appreciate the info above as well, MJ, thank you