b6: (rare) Empty panel
Rare problem that happened by accident. Accidentally clicked the tab of a resource and dragged it slightly to the right before releasing it. It moved the resource tab one to the right but then left the resource window empty. I did it again on purpose and had the same result. In this case I clicked the first tab, drug it slightly to the right, and released. I haven't yet succeeded in getting it to do it a third time. It's easily fixed by clicking a different tab and clicking back. The glitch is shown in the bottom right panel of the screenshot below.
Comments
-
Do you happen to have a log showing this? If you've restarted Logos 4 since getting the empty panel, if it does reoccur, could you attach a log? Thanks.
0 -
I'll be sure to grab logs if I see it again.
0 -
I have a similar bug, but it occurs in my bible pane. As I scroll occasionally the text will disappear, but when I scroll away from the empty space and then scroll back the text will return.
0 -
Dale Eads said:
I have a similar bug, but it occurs in my bible pane. As I scroll occasionally the text will disappear, but when I scroll away from the empty space and then scroll back the text will return.
Sounds like the bug being discussed here:
0 -
Chris Roberts said:
It actually looks quite different. In that other bug, the whole locator bar is visible and the white background of the resources is there, and some text even. In this bug, there's nothing but the panel icon. So very likely the bugs are nowhere near each other in the program code.
0 -
Rosie Perera said:
The error that Dale described above sounds like what I saw when I originated the other thread.
0 -
Dale Eads said:
I have a similar bug, but it occurs in my bible pane. As I scroll occasionally the text will disappear, but when I scroll away from the empty space and then scroll back the text will return.
Dale
As Chris noted in the post immediately following yours, this is probably the bug i described in http://community.logos.com/forums/t/29514.aspx which is different from the one that prompted this thread.
0 -
Jack Caviness said:Rosie Perera said:
The error that Dale described above sounds like what I saw when I originated the other thread.
Ah yes, I hadn't really taken in Dale's post. I was making the comparison between Chris's initial post in this thread and your initial post in that other thread, which do look like different bugs, but you're right, Dale's looks like it might be the same as yours.
0
