[pgadmin-support] pgAdmin 4 v1.0: Problems with high dpi scaling on Win10
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. The short term solution would be to make the app dpi unaware, thus letting Windows take care of the scaling. Here an extract of the page above that seems relevant here: ---snip--- In order to get an application designed for low DPI values running on a high resolution monitors quickly, consider one of the scaling options (let the application run as DPI Unaware on Windows or set the environment variable QT_AUTO_SCREEN_SCALE_FACTOR to "1". These options may incur some scaling or painting artifacts, though. In the longer term, the application should be adapted to run unmodified: - Always use the qreal versions of the QPainter drawing API. - Size windows and dialogs in relation to the screen size. - Replace hard-coded sizes in layouts and drawing code by values calculated from font metrics or screen size ---snip--- pgAdmin III is not affected as it is clearly not dpi aware and therefore scaled by Windows. This leads to blurred text and icons but at least it’s big enough to be legible. Viktor
[pgadmin-support] Build problems on Ubuntu Feisty and possibly on other Linux systems
Hi,
I recently solved a build problem that prevented me from compiling PgAdmin III
1.8.0beta5. Please let you know the details to prevent further problems.
Details:
OS: Ubuntu Feisty, up-to-date (I write here, since PgAdmin cannot be found in
Ubuntu's bug reporting system, and 1.8beta5 is beta software.)
wxWidgets installed: 2.6 by default, and 2.8 from the universe or multiverse
repository. Development files (headers) are also installed for both.
The configure script ran successfully and detected wxWidgets 2.8 correctly,
but chose the base (non-GUI) version, not the GTK one. The script set
wxUSE_GUI to 0 in all Makefiles, that caused houndreds of "not declared"
errors at compile time, when wxWindows or such GUI classes are referenced. I
had to trace back this issue to wx.h, where the #if directive turned off all
GUI includes.
As a quick fix I replaced all instances of "${WX_HOME}/bin/wx-config"
by "/usr/lib/wx/config/gtk2-unicode-release-2.8" (without the double quotes)
in the configure script. This is only a quick fix, not a real solution.
Since PgAdmin III is a GUI only application, it would be useful to force the
wxUSE_GUI flag to be 1, or somehow selecting the correct GUI (not base) wx
version on systems such as Debian Etch and Ubuntu Feisty with
an /etc/alternatives system in place. I know, that this should be the distro
maintainers' problem, but currently compiling from source is the only
solution on such systems and this does not work out of the box.
Please publish this information in PgAdmin III 1.8's FAQ or the installation
instructions to prevent further problems to others.
Thank you, Viktor
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
[pgadmin-support] pgAdmin 1.10.2 issue
Hello! When i wake up my PC from hibernate-state with pgAdmin running and try to do something with opened database, pgAdmin reasonably says about lost connection and closes this database. But waiting cursor still being waiting even if i open datasbe again. -- Best regards, Samokhin Viktor http://wowyupiyo.livejournal.com
Re: [pgadmin-support] pgAdmin 4 v1.0: Problems with high dpi scaling on Win10
On Mon, Oct 3, 2016 at 11:01 AM, Dave Page wrote: > Hi > > On Sun, Oct 2, 2016 at 11:43 PM, 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.
Re: [pgadmin-support] pgAdmin 4 v1.0: Problems with high dpi scaling on Win10
On Mon, Oct 3, 2016 at 1:44 PM, Dave Page wrote: > On Mon, Oct 3, 2016 at 12:32 PM, Dave Page wrote: > > On Mon, Oct 3, 2016 at 11:33 AM, Viktor Trojanovic > wrote: > >> On Mon, Oct 3, 2016 at 11:01 AM, Dave Page wrote: > >>> > >>> Hi > >>> > >>> On Sun, Oct 2, 2016 at 11:43 PM, 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. > > > > :-(. OK, thanks - I've added this thread to > > https://redmine.postgresql.org/issues/1564 where we're tracking issues > > related to this. > > I just figured out how to reproduce this on Windows - it seems like > VMware was confusing matters, but I can see the problem now. I'll > update the ticket. > > BTW; whilst it won't affect the runtime titlebar etc. are you aware > you can use Ctrl+ (depending on your keyboard, you may need to hit > Shift as well to get Ctrl+ rather than Ctrl=) and Ctrl- to zoom the > display? That will allow you to get it to a usable size. > > Hi Dave, Sorry for the late reply. No, I wasn't aware of this. I was trying to do this using the scrollwheel on my mouse while pressing the CTRL-Key, without success. But just using the key combo CTRL-+ works perfectly, it basically solves my problem. Thanks for the hint! Viktor
