https://bugs.kde.org/show_bug.cgi?id=392468
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=412227
Christoph Cullmann changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kat
https://bugs.kde.org/show_bug.cgi?id=412015
Christoph Cullmann changed:
What|Removed |Added
Assignee|kwrite-bugs-n...@kde.org|martin.sandsm...@kde.org
https://bugs.kde.org/show_bug.cgi?id=398586
Christoph Cullmann changed:
What|Removed |Added
CC||zeroping+kdeb...@gmail.com
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=411950
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=411921
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=412014
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
Resolution
https://bugs.kde.org/show_bug.cgi?id=412016
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
Status
https://bugs.kde.org/show_bug.cgi?id=412447
--- Comment #8 from Christoph Cullmann ---
Thanks already for this nice improvement.
I still think that some minimal factor of 0.0625 would be preferable, this
would make the rounding on output unnecessary, too.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=412447
--- Comment #12 from Christoph Cullmann ---
This would be the output code change:
// round to the nearest 1/16 multiple
const double minimalScaleStep = (1. / 16.);
info[QStringLiteral("scale")] = qRound(output->scale() / min
https://bugs.kde.org/show_bug.cgi?id=412447
--- Comment #11 from Christoph Cullmann ---
> Would it work if we internally round it before storing? E.g. f = qRound(f *
> 32) / 32. For displaying, it would use f = qRound(f * 20) / 20. Some testing
> would be needed to confirm thi
https://bugs.kde.org/show_bug.cgi?id=412447
--- Comment #13 from Christoph Cullmann ---
Btw., if you want to read up why such 0.1 or 0.05 things create issues for
computation, take e.g. a look at
https://docs.python.org/3/tutorial/floatingpoint.html
Actually a good explanation why you get very
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #43 from Christoph Cullmann ---
Hi, I would like to backport my patch to stable, is that ok?
Otherwise Kate will just startup as a large artifact on multi-head setups in
many cases.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=412447
--- Comment #10 from Christoph Cullmann ---
Btw., to see the concrete benefit, try out the following:
export QT_SCALE_FACTOR=1.1
use current master version of frameworks + kwrite, open a file, select many
lines and then scale the font up and down
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #112 from Christoph Cullmann ---
This small change fixes 99% of the artifacts for me:
diff --git a/src/TerminalDisplay.cpp b/src/TerminalDisplay.cpp
index 5753ae74..fabf5907 100644
--- a/src/TerminalDisplay.cpp
+++ b/src
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #114 from Christoph Cullmann ---
Git commit 2c10032170ac9c01b71bd4d405c2d7ba40786c68 by Christoph Cullmann.
Committed on 02/10/2019 at 20:54.
Pushed by scmsync into branch 'master'.
fix many of the rendering artifacts for hi-dpi setups
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #117 from Christoph Cullmann ---
*** Bug 406770 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406770
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
Status
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #122 from Christoph Cullmann ---
Git commit b025e4234c8e0d15cf33a392ba3f71c802fc1b2c by Christoph Cullmann.
Committed on 02/10/2019 at 22:43.
Pushed by scmsync into branch 'master'.
anti-alias line character painting, too, with the text
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #122 from Christoph Cullmann ---
Git commit b025e4234c8e0d15cf33a392ba3f71c802fc1b2c by Christoph Cullmann.
Committed on 02/10/2019 at 22:43.
Pushed by scmsync into branch 'master'.
anti-alias line character painting, too, with the text
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #121 from Christoph Cullmann ---
Git commit b025e4234c8e0d15cf33a392ba3f71c802fc1b2c by Christoph Cullmann.
Committed on 02/10/2019 at 22:43.
Pushed by cullmann into branch 'master'.
anti-alias line character painting, too, with the text
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #113 from Christoph Cullmann ---
Git commit 2c10032170ac9c01b71bd4d405c2d7ba40786c68 by Christoph Cullmann.
Committed on 02/10/2019 at 20:54.
Pushed by cullmann into branch 'master'.
fix many of the rendering artifacts for hi-dpi setups
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #114 from Christoph Cullmann ---
Git commit 2c10032170ac9c01b71bd4d405c2d7ba40786c68 by Christoph Cullmann.
Committed on 02/10/2019 at 20:54.
Pushed by scmsync into branch 'master'.
fix many of the rendering artifacts for hi-dpi setups
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #115 from Christoph Cullmann ---
Created attachment 122981
--> https://bugs.kde.org/attachment.cgi?id=122981=edit
pre patch with QT_SCALE_FACTOR=1.5
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #116 from Christoph Cullmann ---
Created attachment 122982
--> https://bugs.kde.org/attachment.cgi?id=122982=edit
post patch with QT_SCALE_FACTOR=1.5
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #118 from Christoph Cullmann ---
For me the other artifacts disappear if I alter:
void TerminalDisplay::processFilters()
to always do a full update instead of
update(preUpdateHotSpots | postUpdateHotSpots);
=> this means here we h
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #119 from Christoph Cullmann ---
Perhaps that was the wrong update(), even if one tweaks that to be a bit more
lax, the ranges are not that right. A better candidate is the
update(dirtyRegion)
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #120 from Christoph Cullmann ---
Modifying what it is done here:
// if the characters on the line are different in the old and the new _image
// then this line must be repainted.
if (updateLine
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #123 from Christoph Cullmann ---
Unfortunately for the remaining artifacts the only local hack I have is to do
// update the parts of the display which have changed
update();
instead of
// update the parts of the display
https://bugs.kde.org/show_bug.cgi?id=390451
Christoph Cullmann changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kte
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #124 from Christoph Cullmann ---
I created bugs for the clipping issues found here and in KTextEditor
https://bugreports.qt.io/browse/QTBUG-78962
https://bugreports.qt.io/browse/QTBUG-78963
If I am not wrong, see no way how Konsole could
https://bugs.kde.org/show_bug.cgi?id=390451
--- Comment #29 from Christoph Cullmann ---
I created bugs for the clipping issues found here and in Konsole.
https://bugreports.qt.io/browse/QTBUG-78962
https://bugreports.qt.io/browse/QTBUG-78963
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=390451
--- Comment #30 from Christoph Cullmann ---
fillRect bug with anti-aliasing reported here
https://bugreports.qt.io/browse/QTBUG-78964
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #125 from Christoph Cullmann ---
fillRect bug with anti-aliasing reported here
https://bugreports.qt.io/browse/QTBUG-78964
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412447
Bug ID: 412447
Summary: Scaling-Level as multiple of 0.25
Product: KScreen
Version: git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=390451
--- Comment #17 from Christoph Cullmann ---
I have some potential fix, that works at least if you use scaling factors that
are proper floating points like 1.25, 1.5, ...
https://cgit.kde.org/ktexteditor.git/log/?h=hidpi-font-fixes
Could somebody give
https://bugs.kde.org/show_bug.cgi?id=412313
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=404907
Christoph Cullmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=411965
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=411965
Christoph Cullmann changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon
https://bugs.kde.org/show_bug.cgi?id=411965
Christoph Cullmann changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #24 from Christoph Cullmann ---
I think I have some fix:
https://invent.kde.org/kde/konsole/merge_requests/33
For me that removes the distortion.
I think winId introduces native widgets in the wrong places.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=390451
Christoph Cullmann changed:
What|Removed |Added
Version Fixed In||5.63
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=390451
Christoph Cullmann changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=412447
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=412447
--- Comment #5 from Christoph Cullmann ---
The main issue is:
0.1 is no floating point value you can represent on a machine.
With factors like 1.1, you get rounding artifacts everywhere.
Even if you scale something trivial like a 10 pixel UI element
https://bugs.kde.org/show_bug.cgi?id=390451
--- Comment #20 from Christoph Cullmann ---
There is nothing to round in virtual pixel.
e.g. if the font is 10 virtual pixel high, you get real 12.5 real pixel if you
scale with 1.25.
KTextEditor will not at all see this and we will get some ugly lines
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #27 from Christoph Cullmann ---
Yep, forgot to reopen ;=)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412420
Christoph Cullmann changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=411965
Christoph Cullmann changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon
https://bugs.kde.org/show_bug.cgi?id=411965
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|https
https://bugs.kde.org/show_bug.cgi?id=411965
Christoph Cullmann changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #32 from Christoph Cullmann ---
For normal konsole starts, I get a useful WINDOWID exported:
declare -x WINDOWID="69206023"
For konsole parts embedded in e.g. Kate, I get not mostly 0.
Perhaps the problem is the way t
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #33 from Christoph Cullmann ---
I debugged a bit more, and yes, for the Kate case, the
widget->nativeParentWidget() function returns nullptr.
Therefore you get some 0 id from the effectiveWinId().
For a normal konsole start, all is f
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #39 from Christoph Cullmann ---
Git commit f295734722808827e3cb0743f6588d01a2ae2a0b by Christoph Cullmann.
Committed on 30/09/2019 at 19:12.
Pushed by scmsync into branch 'Applications/19.08'.
load terminal on demand to have some parent
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #40 from Christoph Cullmann ---
I cherry-picked the Kate change to 19.08.
I will wait for the Konsole devs to judge if the other change is OK.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #38 from Christoph Cullmann ---
Git commit f295734722808827e3cb0743f6588d01a2ae2a0b by Christoph Cullmann.
Committed on 30/09/2019 at 19:12.
Pushed by cullmann into branch 'Applications/19.08'.
load terminal on demand to have some parent
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #37 from Christoph Cullmann ---
With this I think this issue is really solved.
Konsole will never invent bad native widgets and Kate will provide proper
parents.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #31 from Christoph Cullmann ---
And the sad truth here is: whereas this avoid any rendering artifacts, I am not
sure the id is not in most cases just 0, even thought the docs don't hint to
that...
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #35 from Christoph Cullmann ---
Git commit ec4391fb297ff3f91013c7cd4bc5bf82771f516d by Christoph Cullmann.
Committed on 30/09/2019 at 19:09.
Pushed by cullmann into branch 'master'.
load terminal on demand to have some parent widget
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #36 from Christoph Cullmann ---
Git commit ec4391fb297ff3f91013c7cd4bc5bf82771f516d by Christoph Cullmann.
Committed on 30/09/2019 at 19:09.
Pushed by scmsync into branch 'master'.
load terminal on demand to have some parent widget
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #34 from Christoph Cullmann ---
Ok, for Kate I can solve that, the part widget() just needs to have some proper
parent.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411965
--- Comment #42 from Christoph Cullmann ---
We still have some days before the 19.08.2 tagging, I think we can wait for
judgement of the console devs, wrote more stuff to
https://invent.kde.org/kde/konsole/merge_requests/33
Perhaps they want some
https://bugs.kde.org/show_bug.cgi?id=390451
--- Comment #26 from Christoph Cullmann ---
I still want to get rid of factors like 1.1, as they still have lots of small
glitches everywhere as you round the whole time, unlike for 1/16 or so. But at
least with these hacks it not that bad.
I added
https://bugs.kde.org/show_bug.cgi?id=373232
--- Comment #111 from Christoph Cullmann ---
See https://bugreports.qt.io/browse/QTBUG-66036 and
https://bugs.kde.org/show_bug.cgi?id=390451
For me most things already work if we do just remove
paint.setRenderHint(QPainter::Antialiasing
https://bugs.kde.org/show_bug.cgi?id=390451
--- Comment #23 from Christoph Cullmann ---
Git commit 2d6c8f17f5e040ac05ea43ba1726c13c38e806a3 by Christoph Cullmann.
Committed on 01/10/2019 at 20:02.
Pushed by cullmann into branch 'master'.
next rendering artifact goes away if you adjust the clip
https://bugs.kde.org/show_bug.cgi?id=390451
--- Comment #22 from Christoph Cullmann ---
Git commit 165a7a3b526ca70635e36e036e2f9cdd4b5947ce by Christoph Cullmann.
Committed on 01/10/2019 at 19:40.
Pushed by cullmann into branch 'master'.
avoid the font choosing magic and turn of anti aliasing
https://bugs.kde.org/show_bug.cgi?id=390451
Christoph Cullmann changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=390451
Christoph Cullmann changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=390451
--- Comment #27 from Christoph Cullmann ---
And with stuff like 1.1 and some font sizes, you will still get sometimes a
small artifact line ever xx lines. That's just the bad scaling of the rounding.
But I think with that on can live. With some sane
https://bugs.kde.org/show_bug.cgi?id=407103
--- Comment #27 from Christoph Cullmann ---
I would appreciate further tunings.
But perhaps we shall first apply the patch to fix the behavior regressions.
Would you be ok with that and provide some name + mail address to push it?
--
You
https://bugs.kde.org/show_bug.cgi?id=413353
Christoph Cullmann changed:
What|Removed |Added
Ever confirmed|0 |1
CC
https://bugs.kde.org/show_bug.cgi?id=413306
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
https://bugs.kde.org/show_bug.cgi?id=413306
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=413306
Christoph Cullmann changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kat
https://bugs.kde.org/show_bug.cgi?id=414997
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=415036
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
Resolution
https://bugs.kde.org/show_bug.cgi?id=414408
Christoph Cullmann changed:
What|Removed |Added
CC||dshis...@iitb.ac.in
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=413050
Christoph Cullmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=311182
Christoph Cullmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=413232
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=391031
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=407638
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=347570
Christoph Cullmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=413232
--- Comment #3 from Christoph Cullmann ---
You mean the application icons?
Or the icons used in the applications themself? In the applications the breeze
icon set is used.
For the application, we use the icons the maintainers preferred.
--
You
https://bugs.kde.org/show_bug.cgi?id=333090
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
Status
https://bugs.kde.org/show_bug.cgi?id=388280
Christoph Cullmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=413232
Christoph Cullmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=281334
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=305717
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=413158
Christoph Cullmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=412987
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=413039
--- Comment #28 from Christoph Cullmann ---
Could we let the installer rest?
The KDE 4.x stuff is "totally" unmaintained.
Even more on Windows then on Unices.
I remember well the bug reports I had for Kate, that varied from "Ca
https://bugs.kde.org/show_bug.cgi?id=413039
--- Comment #38 from Christoph Cullmann ---
We could try to blacklist the breeze/.../... icon theme folders.
To blacklist all icons has the issue that some applications might install own
ones that are not in the themes we ship as rccs (if I am
https://bugs.kde.org/show_bug.cgi?id=413050
--- Comment #2 from Christoph Cullmann ---
The 100% screenshot is actually 150% ;=)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413050
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=413050
--- Comment #3 from Christoph Cullmann ---
Beside this glitch, Breeze is by far the best scaling style I found.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413050
--- Comment #8 from Christoph Cullmann ---
Created attachment 123250
--> https://bugs.kde.org/attachment.cgi?id=123250=edit
150% Breeze 5.17 without framework integrations
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413050
--- Comment #6 from Christoph Cullmann ---
Perhaps Breeze is even nice as is and the issue is that we compile the
frameworks integration stuff at the moment, I try to fix that (and I see that
we missed to update in craft to latest Breeze...)
--
You
https://bugs.kde.org/show_bug.cgi?id=413050
--- Comment #5 from Christoph Cullmann ---
Because it doesn't work at all if you scale stuff ;=)
See:
https://doc.qt.io/qt-5/highdpi.html
"While the macOS style fully supports high-DPI, the Windows desktop style
currently has some limita
801 - 900 of 3836 matches
Mail list logo
