Bug 99031 - UI shows cursor twice if it is moved manually in the same cell
Summary: UI shows cursor twice if it is moved manually in the same cell
Status: RESOLVED DUPLICATE of bug 96545
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.1.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-01 14:59 UTC by Markus Grob
Modified: 2016-04-04 10:55 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
error on linux (2.01 KB, image/jpeg)
2016-04-01 14:59 UTC, Markus Grob 		Details
error on Windows (2.30 KB, image/jpeg)
2016-04-01 15:00 UTC, Markus Grob 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Grob 2016-04-01 14:59:35 UTC 
Created attachment 124016 [details]
error on linux

The cursor still stays activ at the position until the cell is changed (screenshot).
It was tested with grafic accelleration and without. Also with GL and without. 

Linux (Suse Leap with KDE) with 5.0.4 doesn't show this error, but 5.1.3 shows it. It seems, that the error has entered at 5.0.5, because this version shows the error on Windows 7.

To reproduce:

1. enter something in a cell
2. leave and reenter
3. move the cursor with the cursorkeys an the keyboard
4. a "copy" of the cursor will stay at the position, where the cursor was set first.
Comment 1 Markus Grob 2016-04-01 15:00:09 UTC 
Created attachment 124017 [details]
error on Windows
Comment 2 Markus Grob 2016-04-01 15:02:13 UTC 
As I have seen, I have also 5.1.3 installed on Windows, so I don't really know, on which version the error has come.
Comment 3 raal 2016-04-04 10:55:10 UTC 
Hello,

Thank you for submitting the bug. The bug has previously been reported, so this bug will be added as a duplicate of it. You will automatically be CCed to updates made to the other bug.

*** This bug has been marked as a duplicate of bug 96545 ***