BUG- Search in L5 unstable requires program shutdown

Warren Dane said:

L5 has been open over night and previously I had no problem in searching during 1st day of install. Now on the 2nd day the Bible search doesn't provide a full drop down menu of varied bible passage options and it locks up when seeking to enter a specific search range in scripture. The entire menu line of open books began to jump back and forth with the message at the top "not responding". I have all the available updates for L5. My machine has 6GB RAM, Win7 64bit updated. No previous problems with L4. Now this, out of the blue, after L5 ran perfectly right after being installed and for the 1st day. What's up???

I think this is a bug.

I had something similar to what you are describing during beta testing. The solution was to deal with that line of open books where the icons seemed to be jumping back and forth. To do that, remove one of the books (or tabs) from that pane (also known as: "column") by moving it to an adjacent pane, or by closing it.

Try that and tell me if it works.

It's still a bug, but it has a work around. What happens is that Logos is using it's program time to resolve an issue where the icon widths require an adjustment. But it keeps deciding over and over again to expand or contract one or more of the icons. By removing one of the icons from the pane, Logos stops doing that and does what it's supposed to.

If you can still do it, edit the title of this thread and put the word "BUG:"  as the first word in the thread title (upper right "More" button > "Edit").

Warren Dane said:

Thanks Rich

Before reading your helpful description of the problem I discovered that removing one of the books removed the unstable situation. I put "BUG" on my tag option for the thread. I'll do the edit as well. Hope this bug gets fixed. It's a nuisance, but gratefully, not a stopper.

Warren

It's also not easy to reproduce, as it only occurs when certain resources are loaded to a pane of a certain width, and in a certain order. If you have a screen shot of the offending sequence of tabs, it might enable the program developers to reproduce it and look into a fix.

Tommy Ball said:

Taking a screen-shot + adding logs if either of you can reproduce the bug would be splendid! 

I have not been able to reproduce this, since the pre-release beta period.