BUG: Selecting text with footnotes displayed
The new feature in v4.5 to display footnotes is great, but seems to create a problem in selecting text, in the following situation (see the screen shot below).
1) Display a resource in two columns (without TOC).
2) The right column has a footnote at the bottom, the left column does not.
3) Begin selecting text in the left column a few rows higher than the beginning of the footnote text, dragging the mouse downward in the left column (don't take the mouse pointer into the right column).
4) The problem is that in many instances, the selection cannot be taken below the row in the left column which is at about the same vertical position as the top of the footnote in the right column. In the screen shot below, the text below the shaded text could not be selected. The problem must not be with my mouse, because I experience it with both a wireless Bluetooth mouse and a corded mouse.
If display of footnotes is turned off, the problem goes away and text may be selected even to the bottom of the left column.
Crash report: Sometimes, if I try to start the highlighting in the left column on a row which is about at the height of the top of the footnote (instead of a row higher up), it produces a crash. I submitted crash logs from such a crash in my message "BUG: Logos 4.5 crashing" sent last night.
Comments
-
. I submitted crash logs from such a crash in my message "BUG: Logos 4.5 crashing" sent last night.
Thanks for the extra detail, Keith
Previous thread is http://community.logos.com/forums/t/44722.aspx
Dave
===Windows 11 & Android 13
0 -
Thanks for the detailed bug report! I can reproduce the problems with selection and the crash and have filed a bug report.
0 -
[Y] Thanks for highlighting this bug...and for Logos making a footnote about it... [;)]
0 -
The crash will be fixed in the next update. The selection bug will be listed as a Known Issue.
0 -
The crash will be fixed in the next update. The selection bug will be listed as a Known Issue.
Logos 4.5 SR-5 release notes include fix for this bug.
Keep Smiling [:)]
0