From: | Viktor Trojanovic <viktor(at)troja(dot)ch> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: pgAdmin 4 v1.0: Problems with high dpi scaling on Win10 |
Date: | 2016-10-03 10:33:58 |
Message-ID: | CAL=ybPDtkHHczhBqk6WBwyj9Mg4QfpTcZYqD2er-AQxs6mOZcQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Mon, Oct 3, 2016 at 11:01 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Hi
>
> On Sun, Oct 2, 2016 at 11:43 PM, <viktor(at)troja(dot)ch> wrote:
> > Hi list, hi Dave,
> >
> > On Windows 10 using a high res screen with high dpi scaling turned on and
> > set to 200%, the text in the pgAdmin 4 (standalone) interface becomes
> almost
> > illegible.
> >
> > The issue seems to be that pgAdmin claims to Windows that is high dpi
> aware
> > when it actually isn’t. See http://doc.qt.io/qt-5/highdpi.html for more
> info
> > about how QT deals with high dpi issues.
>
> I think it's more subtle than that. Most of the dev team run Macs, and
> high dpi support seems to work fine for us. We have had some issues
> reported - but on my retina MBP for example, pgAdmin displays nicely
> at all scaling levels.
>
> > The short term solution would be to make the app dpi unaware, thus
> letting
> > Windows take care of the scaling.
>
> Have you tried setting QT_AUTO_SCREEN_SCALE_FACTOR? Does it make a
> difference on Windows?
>
>
I can confirm that setting the environment variable
QT_AUTO_SCREEN_SCALE_FACTOR=1, or 0 for that matter, makes no difference.
I even tried setting the following parameters in your qt.conf:
[Platforms]
WindowsArguments = dpiawareness=0 (and 1, and 2)
without any effect.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2016-10-03 11:28:50 | Re: pgAdmin4 - Query Tool stuck "Initializing the query execution!" on localhost |
Previous Message | Jan Rössler | 2016-10-03 09:57:34 | Re: pgAdmin4 - Query Tool stuck "Initializing the query execution!" on localhost |