[Development] Fwd: Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

Lisandro Damián Nicanor Pérez Meyer perezmeyer at gmail.com
Tue Sep 5 14:16:47 CEST 2017


---------- Mensaje reenviado ----------
De: "Samuel Thibault" <sthibault at debian.org>
Fecha: 5 sep. 2017 5:40 a.m.
Asunto: Re: [Development] Bug#874054: Setting
QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact,
should not be always on
Para: "Frederik Gladhorn" <frederik.gladhorn at qt.io>
Cc: <development at qt-project.org>, "Allan Sandfeld Jensen" <kde at carewolf.com>,
<debian-qt-kde at lists.debian.org>, "Sebastian Humenda" <shumenda at gmx.de>, <
874054 at bugs.debian.org>, "Lisandro Damián Nicanor Pérez Meyer" <
lisandro at debian.org>, "Alex ARNAUD" <alexarnaud at hypra.fr>

Hello,

It seems my mails don't reach the development at qt-project.org mailing
list. Could somebody who got them forward them to it?

Frederik Gladhorn, on mar. 05 sept. 2017 10:32:43 +0200, wrote:
> And then Allan is right, by setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON you
ask
> for it. All the stuff unconditionally. Please don't, why do you need it
in the
> first place?

Because it would just not work at all in non-kde desktops in Debian 9
otherwise (and I didn't notice performance regression). AIUI, qt 5.7 was
only looking at the "accessibility enabled" checkbox in kde
configuration.

> Right now Qt is trying to emulate Gnome's way, except since we don't
> listen to the change signal, we never dynamically enable/disable a11y.

With Debian testing (qt 5.9), I don't need to set
QT_LINUX_ACCESSIBILITY_ALWAYS_ON, and accessibility seems to get enabled
dynamically, so it seems something changed between 5.7 and 5.9.

Samuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20170905/368dbd10/attachment.html>


More information about the Development mailing list