BUG: 5.2 SR-3 (Win): Selection anchor lost when scrolling
Sometimes when I'm dragging a selection downward in a resource, as soon as the resource starts to scroll down, the anchor from the beginning of the selection suddenly jumps to a new location.
This one is hard to reproduce consistently, but by trying over and over several times I was able to get a screen capture video of it happening. Here's a link to that: http://www.screencast.com/t/TLqSdcsz (the jump happens at about 3 seconds in). And attached is the log file from that session.
Here's a freeze-frame from the video showing where the selection started:
And here's a freeze-frame showing where the anchor has suddenly jumped to a new location, without me releasing the mouse button at all:
It's a rather short chapter, only a screen or two worth. Certainly nowhere as long as the maximum allowable selection.
Comments
-
Thanks for capturing this ... it had been reported but not documented.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:
Thanks for capturing this ... it had been reported but not documented.
I have been so frustrated tonight! The first time in quite a while that I've sat down and tried to use Logos to get some actual work done (planning a worship service for this Sunday), and I cannot get very far before running into another bug that I need to document, or a needing to make up a huge list of books by an important author Logos is missing. Arggh! Up way too late.
0 -
Thank you for providing the screencast. I can now reproduce the issue and have created a case for it.
0 -
Chris Culy (Logos) said:
Thank you for providing the screencast. I can now reproduce the issue and have created a case for it.
Thank you. That warms my heart!
When I was a developer on the Microsoft Word team, we had a bug that produced this very same behavior, and I was the one who tracked it down and fixed it. Some of the selection code in Word might still have my fingerprints on it, since that was one of my areas. That's why I was so intrepid in getting a reproducible case of this in Logos and recording it.
0 -
Chris Culy (Logos) said:
Thank you for providing the screencast. I can now reproduce the issue and have created a case for it.
This will be fixed in 5.2 SR4.
0 -
That's good news. Thanks!
0
