Bug 304667 - cursor doesn't restore background correctly when 'unblinking'
Summary: cursor doesn't restore background correctly when 'unblinking'
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.8.90
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-08-06 13:32 UTC by Maurits Lamers
Modified: 2018-10-27 02:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
screenshot of the problem, using MonoSpace as font (1.21 KB, image/png)
2012-08-06 16:23 UTC, Maurits Lamers
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maurits Lamers 2012-08-06 13:32:58 UTC
When editing a text which is in italics, some characters will have a part of it drawn at the cursors location, a d for example (using Monaco). 
When putting the cursor behind this d, the cursor will blink over the stem of the d, but when it 'unblinks' it just paints the background color, instead of the stem of the d.
The result is that the character almost reads as an a, instead of a d.

Reproducible: Always

Steps to Reproduce:
1. write a d in an italics font, in such a way that the cursor will overpaint part of the character.
2. put the cursor behind this character
3. Look carefully when the cursor disappears
Actual Results:  
A truncated character, the pixels the cursor took are repainted in the configured background color

Expected Results:  
A complete character, without truncation

Using Ubuntu 12.04, 
Kate Version 3.8.4
Using KDE Development Platform 4.8.4 (4.8.4)
Font used: Monaco
Comment 1 Maurits Lamers 2012-08-06 14:31:22 UTC
After looking a bit more closely, the problem doesn't always arise as I described above. 
A d in the middle of a word for example doesn't show the problem, but a d followed by a ) does show the problem
Comment 2 Dominik Haumann 2012-08-06 15:25:55 UTC
Cannot reproduce with other fonts (I don't have Monaco at hand atm). Are there other fonts with this issue? Does this depend on the font size?
Comment 3 Maurits Lamers 2012-08-06 16:23:50 UTC
Created attachment 72988 [details]
screenshot of the problem, using MonoSpace as font

I managed to make a screenshot of the problem. While Monaco is my standard font, it also turns out to happen when using MonoSpace.
Comment 4 Christoph Cullmann 2012-11-01 00:08:29 UTC
Sorry, can't reproduce either :(
Perhaps some problem with 12.04 on your machine or just hard to reproduce, but in any case, without some way to do so, can't fix this :( Sorry :(
Comment 5 Andrew Crouthamel 2018-09-23 02:41:37 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 02:54:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!