Bug 162328 - fat symbols are higher than one line and cause visual artefacts
Summary: fat symbols are higher than one line and cause visual artefacts
Status: RESOLVED LATER
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-19 20:48 UTC by Armin Berres
Modified: 2011-08-21 06:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing the problem (91.95 KB, image/png)
2008-05-19 20:49 UTC, Armin Berres
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Armin Berres 2008-05-19 20:48:35 UTC
Version:            (using Devel)
Installed from:    Compiled sources

When viewing threads with mutt one can see some visual artefacts, because the arrows used by mutt to view the thread are larger than one line. When on moves to the next line konsole just erases one line and not the pixels it has drawn above this line.
Because a picture shows more than a thousand words have a look at the attached sreenshot. You can clearly see the artefacts and the to large arrow in the highlighted line.

With konsole from KDE 3 I didn't have this problem.
I tried different fonts (termius, dejavu, monospace), all with the same problem.
Comment 1 Armin Berres 2008-05-19 20:49:14 UTC
Created attachment 24854 [details]
Screenshot showing the problem
Comment 2 Robert Knight 2008-06-02 09:55:43 UTC
Confirmed, line drawing code does not take into account the width of the pen.
Comment 3 Armin Berres 2009-04-25 19:04:51 UTC
Maybe this is related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524062 ?
Comment 4 Kurt Hindenburg 2009-08-30 04:46:12 UTC
Here's the Qt bug report

http://qt.nokia.com/developer/task-tracker/index_html?method=entry&id=252925
Comment 5 Jekyll Wu 2011-08-15 05:10:05 UTC
Is this still a issue?

The bug report on Debian is closed as 'fixed upstream in qt-4.6', while the Qt bug report[1] is closed in a confusing way.

https://bugreports.qt.nokia.com/browse/QTBUG-4045