mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Nah don't have to rush for 3.0, that one is canned for any new features.
While we do have macOS CI setup with Travis (
https://travis-ci.org/Mudlet/Mudlet), any sort of macOS-specific
development requires me opening up my 800x600 hackintosh vm and slowly
pecking away at the keys, so any fixes/improvements for that platform would
be welcome. A lot of Mudlet's UI looks out of place on a mac for example -
fields too small and things like that - whereas it looks quite fine on a
windows/linux setup.

Let me know how you go with the HiDPI option and if'd like immediate help,
hop over to https://gitter.im/Mudlet/Mudlet!

On Mon, Mar 13, 2017 at 1:51 PM Colin Gannon <cmgannon26@xxxxxxxxx> wrote:

> I should have some time tomorrow as there's some nasty weather headed my
> way. :) Sorry for the delay, in any case - work has been a little wild.
>
> Are you looking to get this in for the 3.0 release? Also, in response to
> comments regarding HiDPI on MacOS - Apple is actually sane in how they
> reason about scaling and as result MacOS doesn't use the awful logic that
> MSFT does so this issue is specific to HiDPI displays (> FHD) on Windows
> only.
>
> Not to split this thread/conflate issues, but what's the specific need for
> a MacOS dev/platform? Builds? If so, I may be able to accommodate that if
> we set up post-commit webhooks for the Github repo to do CI on an iMac I
> have (it's currently mostly idle). Otherwise I'm happy to contribute on
> issues/enhancements specific to the platforms I use - granted, I'm
> primarily a Python developer and application security guy but I can take a
> whack at some C++/qt. :)
>
> Thanks,
>
> Colin
>
> On Mar 12, 2017 12:50 AM, "Vadim Peretokin" <vperetokin@xxxxxxxxx>
> wrote:
>
> > @Colin: any update on this?
> >
> > On Mon, Mar 6, 2017 at 12:51 PM Vadim Peretokin <vperetokin@xxxxxxxxx>
> > wrote:
> >
> > > Why wouldn't it? Colin has already demonstrated in a screenshot:
> > >
> > > https://bugs.launchpad.net/mudlet/+bug/1652413/+
> > attachment/4797276/+files/wenvvar.PNG
> > >
> > > --
> > > You received this bug notification because you are a member of Mudlet
> > > Makers, which is subscribed to Mudlet.
> > > https://bugs.launchpad.net/bugs/1652413
> > >
> > > Title:
> > >   DPI Awareness/Scaling Issues (Win10)
> > >
> > > Status in Mudlet:
> > >   New
> > >
> > > Bug description:
> > >   Summary:
> > >   Mudlet exhibits behavior associated with static size values (in
> pixels)
> > > in the Qt GUI widgets rather than using relative values. Additionally,
> > the
> > > application does not specify DPI awareness such that Qt autoscales the
> > > application using the native Windows display APIs.* As such, the UI is,
> > > while usable, not properly rendered which breaks third-party UI add-ons
> > > produced by the community.
> > >
> > >   *More info here: http://doc.qt.io/qt-5/highdpi.html
> > >
> > >   Recommended remediation (up for discussion!):
> > >   While an effort to convert Mudlet's QML to relative values would be
> the
> > > "right" fix, the autoscaling provided by Qt 5.6+ and Windows 8.1+ allow
> > for
> > > one of the following:
> > >
> > >      The addition of a qt.conf directive to specify an equivalent of
> the
> > > following (passed at runtime, instructs Windows to treat the
> application
> > as
> > > non-DPI aware and to scale it automatically):
> > >         -platform windows:dpiawareness=0
> > >
> > >   OR
> > >
> > >      The addition of the following property setter for Windows builds
> to
> > > achieve the same goal as option #1:
> > >          QGuiApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
> > >
> > >   Steps to reproduce:
> > >   Run the application on a High DPI Windows 10 machine such as a
> > Microsoft
> > > Surface or 4K display with scaling enabled and set to a value other
> than
> > > 100%. Observe the UI scaling issues in the splash frame and Connections
> > > frame - particularly cut off text and oddly shaped fields/tiny small
> > icons.
> > >
> > >   I have tested the -platform windows:dpiawareness=0 solution and it's
> > >   working with Mudlet3-iota built against Qt5.6 on Windows 10 following
> > >   the wiki instructions. I am building and testing the second (probably
> > >   preferable) fix.
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/mudlet/+bug/1652413/+subscriptions
> > >
> > > _______________________________________________
> > > Mailing list: https://launchpad.net/~mudlet-makers
> > > Post to     : mudlet-makers@xxxxxxxxxxxxxxxxxxx
> > > Unsubscribe : https://launchpad.net/~mudlet-makers
> > > More help   : https://help.launchpad.net/ListHelp
> > >
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1652413
> >
> > Title:
> >   DPI Awareness/Scaling Issues (Win10)
> >
> > Status in Mudlet:
> >   New
> >
> > Bug description:
> >   Summary:
> >   Mudlet exhibits behavior associated with static size values (in pixels)
> > in the Qt GUI widgets rather than using relative values. Additionally,
> the
> > application does not specify DPI awareness such that Qt autoscales the
> > application using the native Windows display APIs.* As such, the UI is,
> > while usable, not properly rendered which breaks third-party UI add-ons
> > produced by the community.
> >
> >   *More info here: http://doc.qt.io/qt-5/highdpi.html
> >
> >   Recommended remediation (up for discussion!):
> >   While an effort to convert Mudlet's QML to relative values would be the
> > "right" fix, the autoscaling provided by Qt 5.6+ and Windows 8.1+ allow
> for
> > one of the following:
> >
> >      The addition of a qt.conf directive to specify an equivalent of the
> > following (passed at runtime, instructs Windows to treat the application
> as
> > non-DPI aware and to scale it automatically):
> >         -platform windows:dpiawareness=0
> >
> >   OR
> >
> >      The addition of the following property setter for Windows builds to
> > achieve the same goal as option #1:
> >          QGuiApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
> >
> >   Steps to reproduce:
> >   Run the application on a High DPI Windows 10 machine such as a
> Microsoft
> > Surface or 4K display with scaling enabled and set to a value other than
> > 100%. Observe the UI scaling issues in the splash frame and Connections
> > frame - particularly cut off text and oddly shaped fields/tiny small
> icons.
> >
> >   I have tested the -platform windows:dpiawareness=0 solution and it's
> >   working with Mudlet3-iota built against Qt5.6 on Windows 10 following
> >   the wiki instructions. I am building and testing the second (probably
> >   preferable) fix.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/mudlet/+bug/1652413/+subscriptions
> >
>
> --
> You received this bug notification because you are a member of Mudlet
> Makers, which is subscribed to Mudlet.
> https://bugs.launchpad.net/bugs/1652413
>
> Title:
>   DPI Awareness/Scaling Issues (Win10)
>
> Status in Mudlet:
>   New
>
> Bug description:
>   Summary:
>   Mudlet exhibits behavior associated with static size values (in pixels)
> in the Qt GUI widgets rather than using relative values. Additionally, the
> application does not specify DPI awareness such that Qt autoscales the
> application using the native Windows display APIs.* As such, the UI is,
> while usable, not properly rendered which breaks third-party UI add-ons
> produced by the community.
>
>   *More info here: http://doc.qt.io/qt-5/highdpi.html
>
>   Recommended remediation (up for discussion!):
>   While an effort to convert Mudlet's QML to relative values would be the
> "right" fix, the autoscaling provided by Qt 5.6+ and Windows 8.1+ allow for
> one of the following:
>
>      The addition of a qt.conf directive to specify an equivalent of the
> following (passed at runtime, instructs Windows to treat the application as
> non-DPI aware and to scale it automatically):
>         -platform windows:dpiawareness=0
>
>   OR
>
>      The addition of the following property setter for Windows builds to
> achieve the same goal as option #1:
>          QGuiApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
>
>   Steps to reproduce:
>   Run the application on a High DPI Windows 10 machine such as a Microsoft
> Surface or 4K display with scaling enabled and set to a value other than
> 100%. Observe the UI scaling issues in the splash frame and Connections
> frame - particularly cut off text and oddly shaped fields/tiny small icons.
>
>   I have tested the -platform windows:dpiawareness=0 solution and it's
>   working with Mudlet3-iota built against Qt5.6 on Windows 10 following
>   the wiki instructions. I am building and testing the second (probably
>   preferable) fix.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1652413/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mudlet-makers
> Post to     : mudlet-makers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mudlet-makers
> More help   : https://help.launchpad.net/ListHelp
>