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 Behalf Of
> >> Christoph Cullmann
> >> Sent: 01 October 2019 22:19
> >> To: development@qt-project.org
> >> Subject: Re: [Development] Updated high-DPI support for Qt 5.14
> >>
> >> Hi,
> >>
> >> actually, unrelated to how one ca
cking the screen. But there might be
other cases such as painting on a intermediate pixmap which needs fixing.
Morten
>
> Mark
>
>> -Original Message-
>> From: Development On Behalf Of
>> Christoph Cullmann
>> Sent: 01 October 2019 22:19
>> To
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-660
> 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-66036
>
> For some I made now h
scaling (if any).
Mark
> -Original Message-
> From: Development On Behalf Of
> Christoph Cullmann
> Sent: 01 October 2019 22:19
> To: development@qt-project.org
> Subject: Re: [Development] Updated high-DPI support for Qt 5.14
>
> Hi,
>
> actually, unrelat
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?
On Friday, 27 September 2019 10:51:00 PDT Morten Sørvig wrote:
> > The problem on that one is that you're forcing me to keep a value per each
> > individual monitor I connect to regularly. With the laptop's display
> > panel, that's 4 or 5. Since they are different actual monitors, each has
> > th
> On 27 Sep 2019, at 17:04, Thiago Macieira wrote:
>
> On Friday, 27 September 2019 03:56:44 PDT Morten Sørvig wrote:
>> Configuring Windows is a good example here: you set the slider to one of
>> 100% - 125% - 150% - 175% - 200% depending on monitor pixel density and
>> viewing distance. There
On Friday, 27 September 2019 03:56:44 PDT Morten Sørvig wrote:
> Configuring Windows is a good example here: you set the slider to one of
> 100% - 125% - 150% - 175% - 200% depending on monitor pixel density and
> viewing distance. There’s then a single value to configure.
Well, that's a good exam
> On 26 Sep 2019, at 04:48, Thiago Macieira wrote:
>
> On Wednesday, 25 September 2019 05:54:20 PDT Morten Sørvig wrote:
>> I see two differences between setting the DPI vs a factor:
>>
>> - You set one value per screen (DPI) instead of two (DPI & factor)
>>
>> - Qt can compute the factor, ac
On Thursday, 26 September 2019 21:07:38 CEST Thiago Macieira wrote:
> On Thursday, 26 September 2019 08:03:32 PDT Edward Welbourne wrote:
> > If possible, I’d like us to move away from relying on setting
> > environment
> > variables, and/or switch to specifying per-screen DPI instea
On Thursday, 26 September 2019 08:03:32 PDT Edward Welbourne wrote:
> If possible, I’d like us to move away from relying on setting
> environment
> variables, and/or switch to specifying per-screen DPI instead of a
> scale
> factor.
>
> On Thursday, 26 September 2019 04:48
If possible, I’d like us to move away from relying on setting
environment
variables, and/or switch to specifying per-screen DPI instead of a scale
factor.
On Thursday, 26 September 2019 04:48:26 CEST Thiago Macieira wrote:
>>> Sure, but where, on X11?
On Thursday, 26 September
On Thursday, 26 September 2019 00:08:34 PDT Allan Sandfeld Jensen wrote:
> On Thursday, 26 September 2019 04:48:26 CEST Thiago Macieira wrote:
> > > If possible, I’d like us to move away from relying on setting
> > > environment
> > > variables, and/or switch to specifying per-screen DPI instead of
On Thursday, 26 September 2019 09:29:10 CEST Shawn Rutledge wrote:
> KDE also needs to set env variables to get correct behavior, right? Which
> ones does it do right? Which ones are wrong or unnecessary in 5.14?
KDE sets the Qt environment variables to set the right scaling. GNOME has
their ow
On Sep 26, 2019, at 9:08, Allan Sandfeld Jensen wrote:
> On Thursday, 26 September 2019 04:48:26 CEST Thiago Macieira wrote:
>>> If possible, I’d like us to move away from relying on setting environment
>>> variables, and/or switch to specifying per-screen DPI instead of a scale
>>> factor.
>>
On Thursday, 26 September 2019 04:48:26 CEST Thiago Macieira wrote:
> > If possible, I’d like us to move away from relying on setting environment
> > variables, and/or switch to specifying per-screen DPI instead of a scale
> > factor.
>
> Sure, but where, on X11?
xrandr?
We read the X11 setting
Hi,
Am 25.09.2019 um 12:33 hat Matthew Woehlke geschrieben:
As a user, I don't want to have to know/measure/compute the DPI of my
display device. I just want to make "stuff" bigger or smaller.
Exactly! As a (Windows) *user* I want Qt based applications (which a
user is probably not aware of be
Den tors 26 sep. 2019 kl 04:51 skrev Thiago Macieira
:
>
> On Wednesday, 25 September 2019 11:08:39 PDT Elvis Stansvik wrote:
> > Large parts of the world did not grow up with inches. I know I'd have
> > a hard time to hold up my fingers to show an inch...
>
> For most people, "DPI" is an arbitrary
On Wednesday, 25 September 2019 11:08:39 PDT Elvis Stansvik wrote:
> Large parts of the world did not grow up with inches. I know I'd have
> a hard time to hold up my fingers to show an inch...
For most people, "DPI" is an arbitrary number ranging from 72 to 288...
--
Thiago Macieira - thiago.ma
On Wednesday, 25 September 2019 05:54:20 PDT Morten Sørvig wrote:
> I see two differences between setting the DPI vs a factor:
>
> - You set one value per screen (DPI) instead of two (DPI & factor)
>
> - Qt can compute the factor, according to policy set by the application (as
> mentioned above)
Den ons 25 sep. 2019 kl 20:51 skrev Kai Pastor, DG0YT :
>
> Am 25.09.19 um 20:08 schrieb Elvis Stansvik:
> > Den ons 25 sep. 2019 kl 18:34 skrev Matthew Woehlke
> > :
> >> On 25/09/2019 08.54, Morten Sørvig wrote:
> >>> I see two differences between setting the DPI vs a factor:
> >>>
> >>> - You se
Am 25.09.19 um 20:08 schrieb Elvis Stansvik:
Den ons 25 sep. 2019 kl 18:34 skrev Matthew Woehlke
:
On 25/09/2019 08.54, Morten Sørvig wrote:
I see two differences between setting the DPI vs a factor:
- You set one value per screen (DPI) instead of two (DPI & factor)
- Qt can compute the facto
Den ons 25 sep. 2019 kl 18:34 skrev Matthew Woehlke :
>
> On 25/09/2019 08.54, Morten Sørvig wrote:
> > I see two differences between setting the DPI vs a factor:
> >
> > - You set one value per screen (DPI) instead of two (DPI & factor)
> >
> > - Qt can compute the factor, according to policy set
On 25/09/2019 08.54, Morten Sørvig wrote:
> I see two differences between setting the DPI vs a factor:
>
> - You set one value per screen (DPI) instead of two (DPI & factor)
>
> - Qt can compute the factor, according to policy set by the application (as
> mentioned above)
>
> [...]
>
> If poss
> On 24 Sep 2019, at 17:54, Thiago Macieira wrote:
>
> On Monday, 16 September 2019 06:00:27 PDT Morten Sørvig wrote:
>> Could KDE possibly set per-screen DPI instead of a scale factor?
>> Applications can now use the
>> QGuiApplication::setHighDpiScaleFactorRoundingPolicy() API to decide wethe
On Monday, 16 September 2019 06:00:27 PDT Morten Sørvig wrote:
> Could KDE possibly set per-screen DPI instead of a scale factor?
> Applications can now use the
> QGuiApplication::setHighDpiScaleFactorRoundingPolicy() API to decide wether
> or not they accept fractional devicePixelRatios (in the ca
> On 16 Sep 2019, at 15:21, Florian Bruhin wrote:
>
> Looks like that change didn't add a changelog entry and didn't bother to
> update
> the documentation at all…
I’ve updated https://wiki.qt.io/New_Features_in_Qt_5.14 . We’ll add similar
content to the change log once it gets posted.
The
On Monday, 16 September 2019 15:21:38 CEST Florian Bruhin wrote:
> I guess with "in 2016" you mean the change this email is talking about:
> https://codereview.qt-project.org/c/qt/qtbase/+/176381
>
> That commit was merged for Qt 5.14 a couple of weeks ago, not in 2016:
Oops! Yes, that's the chan
Hey,
On Mon, Sep 16, 2019 at 07:43:29AM +, Paul Tvete wrote:
> On Friday, 13 September 2019 17:14:32 CEST Thiago Macieira wrote:
>
> > What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
>
> QT_AUTO_SCREEN_SCALE_FACTOR was deprecated in 2016. The recommended
> replacem
> On 13 Sep 2019, at 17:50, Thiago Macieira wrote:
>
> On Friday, 13 September 2019 08:35:59 PDT Elvis Stansvik wrote:
>>> What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
>>
>> I wonder too. I assume they've not been removed? The latter is the one that
>> KDEs kscreen
Den mån 16 sep. 2019 kl 09:44 skrev Paul Tvete :
>
> On Friday, 13 September 2019 17:14:32 CEST Thiago Macieira wrote:
>
> > What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
>
> QT_AUTO_SCREEN_SCALE_FACTOR was deprecated in 2016. The recommended
> replacement is QT_ENABLE_H
On Friday, 13 September 2019 17:14:32 CEST Thiago Macieira wrote:
> What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
QT_AUTO_SCREEN_SCALE_FACTOR was deprecated in 2016. The recommended
replacement is QT_ENABLE_HIGHDPI_SCALING.
It looks like QT_SCREEN_SCALE_FACTORS was
Den fre 13 sep. 2019 kl 17:51 skrev Thiago Macieira :
>
> On Friday, 13 September 2019 08:35:59 PDT Elvis Stansvik wrote:
> > > What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
> >
> > I wonder too. I assume they've not been removed? The latter is the one that
> > KDEs kscr
On Friday, 13 September 2019 08:35:59 PDT Elvis Stansvik wrote:
> > What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
>
> I wonder too. I assume they've not been removed? The latter is the one that
> KDEs kscreen KCM manipulates AFAIK, and I occasionally use it from command
Den fre 13 sep. 2019 17:15Thiago Macieira skrev:
> On Friday, 13 September 2019 06:43:30 PDT Morten Sørvig wrote:
> > * Environment variables for development and testing:
> >
> > - QT_SCALE_FACTOR : enables devicePixelRatio scaling in
> > QtGui, applies a global scale factor. - Q
On Friday, 13 September 2019 06:43:30 PDT Morten Sørvig wrote:
> * Environment variables for development and testing:
>
> - QT_SCALE_FACTOR : enables devicePixelRatio scaling in
> QtGui, applies a global scale factor. - QT_ENABLE_HIGHDPI_SCALING [new] :
> enables devicePixelRatio
Hi all,
We’ve recently merged several patches which improves Qt’s high-DPI support. The
changes include:
* Support for fractional device pixel ratios (e.g. Windows 150%)
* Support per-screen DPI in more places like QStyle
* Cleanup of configuration API and options.
These fixes applies mostly to
39 matches
Mail list logo
