On 2021-09-13 11:19, Volker Hilsheimer wrote:
Hi Christoph,
I just cherry-picked the fix down into 6.2.0, the release team should
be able to stage the fix for the RC.
Great, thanks!
Greetings
Christoph
--
Ignorance is bliss...
https://cullmann.io | https://kate-editor.org
___
Hi,
perhaps this is the wrong place to raise this, but could one reconsider
to have the trivial fix for the more or less duplicated bugs
https://bugreports.qt.io/browse/QTBUG-96285
https://bugreports.qt.io/browse/QTBUG-96359
in Qt 6.2.0?
Without that fix, more or less all applications that use
On 2020-06-11 17:23, Philippe wrote:
I hardly see many users that need to stick to an old Windows version to
be keen,
on another hand, to update to the brand new Qt 6.
That would be paradoxal, few would do this.
And that's not the end of Qt for these Windows 7 users anyway, as they
will be able
Hi,
On 2020-02-13 19:29, Thiago Macieira wrote:
On Thursday, 13 February 2020 09:53:11 PST Thiago Macieira wrote:
I can confirm krdc is affected just the same way that KMail and
VirtualBox
are: it works on screen 1, but fails to repaint on screen 2.
It's a much simpler application than KMail
On 2019-10-04 12:38, Morten Sørvig wrote:
On 3 Oct 2019, at 09:44, Mark De Wit wrote:
Is there a chance that the high-dpi work will fix the dpi-awareness of
the Fusion theme as reported in
https://bugreports.qt.io/browse/QTBUG-74100 ?
Yes, looks like an easy fix:
https://codereview.qt-proje
On 2019-10-03 13:42, Morten Sørvig wrote:
On 1 Oct 2019, at 23:18, Christoph Cullmann
wrote:
Hi,
actually, unrelated to how one can configure the stuff, at the moment,
I see still a lot of Qt internal rendering artifacts for fractional
scaling.
See https://bugreports.qt.io/browse/QTBUG
Hi,
actually, unrelated to how one can configure the stuff, at the moment,
I see still a lot of Qt internal rendering artifacts for fractional
scaling.
See https://bugreports.qt.io/browse/QTBUG-66036
For some I made now hacky workarounds in KTextEditor, see
https://bugs.kde.org/show_bug.cgi?
ort expires next year, I guess it will take at least 1-2
years until
it really kind of expires.
If 5.3 and upwards will drop XP support, many people needing
XP will be forced to skip new features (and non-critial bugfixes or perf.
improvements that are not backported).
Greetings
Christoph
--
-
