On 12/07/17 11:44, Friedemann Kleint wrote:
small update; The proposed change
https://codereview.qt-project.org/#/c/199789/ compiles now. If you build
Qt yourself, you should be able to use it.
Thanks!
Is this change targeting a 5.9.x version, or will I have to build Qt
every time myself
Hi,
small update; The proposed change
https://codereview.qt-project.org/#/c/199789/ compiles now. If you build
Qt yourself, you should be able to use it.
Regards, Friedemann
--
Friedemann Kleint
The Qt Company GmbH
___
Interest mailing list
On terça-feira, 11 de julho de 2017 04:17:37 PDT Nikos Chantziaras wrote:
> Thanks. Seems I'm stuck with MinGW. MSVC, even the latest 2017 version,
> is completely incapable of even remotely being able to build the C11
> part of my code-base.
That's because it's not a C11 compiler. It's not even
On 11/07/17 13:41, Friedemann Kleint wrote:
Hi,
>On 07.07.2017 10:04, Nikos Chantziaras wrote:
>I was battling with accessibility issues for a while now, where Qt was
not exposing IAccessible2 interfaces, making Qt application almost
completely inaccessible.
>An NVDA developer figured out
Hi,
>On 07.07.2017 10:04, Nikos Chantziaras wrote:
>I was battling with accessibility issues for a while now, where Qt was
not exposing IAccessible2 interfaces, making Qt application almost
completely inaccessible.
>An NVDA developer figured out that it's because MinGW builds of Qt
don't seem
I was battling with accessibility issues for a while now, where Qt was
not exposing IAccessible2 interfaces, making Qt application almost
completely inaccessible.
An NVDA developer figured out that it's because MinGW builds of Qt don't
seem to support COM interfaces. This was nowhere to be
