Hello,
It seems my mails don't reach the developm...@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
I'm a bit split here, let's try to find some middle ground :)
I do think that we should always run with accessibility enabled and we don't
do that for a reason.
One thing to fix for linux accessibility is listening to the change signal on
for a11y being enabled or not. If I recall correctly list
Lisandro Damián Nicanor Pérez Meyer, on dim. 03 sept. 2017 19:08:38 -0300,
wrote:
> So you mean that something changed between 5.7 and 5.9?
It seems so.
Samuel
El 3 sep. 2017 4:39 p.m., "Samuel Thibault" escribió:
Samuel Thibault, on dim. 03 sept. 2017 21:17:12 +0200, wrote:
> I have checked with a vanilla reinstall of Debian 9, using the Mate
> desktop, and Qt 5.7.1.
>
> When QT_LINUX_ACCESSIBILITY_ALWAYS_ON is not set, I don't see Qt
> applications in
Control: clone -1 -2
Control: reassign -2 at-spi2-core
Control: retitle -2 Should not set QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 any more
Control: found -1 5.7.1+dfsg-3+b1
Control: done -1 5.9.1+dfsg-9
Samuel
Samuel Thibault, on dim. 03 sept. 2017 21:17:12 +0200, wrote:
> I have checked with a vanilla reinstall of Debian 9, using the Mate
> desktop, and Qt 5.7.1.
>
> When QT_LINUX_ACCESSIBILITY_ALWAYS_ON is not set, I don't see Qt
> applications in accerciser, only the Mate applications. If I set
> QT_
Samuel Thibault, on dim. 03 sept. 2017 20:23:30 +0200, wrote:
> Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:19:31 +0200, wrote:
> > On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote:
> > > Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
> > >
> > > That's Qt
On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote:
> Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
>
> That's Qt's fault for not taking care of EventListenerRegistered
> signals to determine whether someone is listening.
>
So it is Qt's fault that is doing wh
Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:31:58 +0200, wrote:
> Note, the case where I saw the largest performance impact was not moving
> the cursor, it was self-modifying web-content, it would send every text
> change
> in the active focus. [...]
> But it is what Chrome would send on mac
On Sonntag, 3. September 2017 20:23:30 CEST Samuel Thibault wrote:
> Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:19:31 +0200, wrote:
> > On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote:
> > > Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
> > >
> > > That
Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:19:31 +0200, wrote:
> On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote:
> > Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
> >
> > That's Qt's fault for not taking care of EventListenerRegistered
> > signals to d
Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
> On Sonntag, 3. September 2017 18:15:15 CEST Samuel Thibault wrote:
> > On the long run, it really should. Just hiding issues is not the way
> > forward :)
> >
> > Also, note that if the performance is so bad, it means something
On Sonntag, 3. September 2017 18:15:15 CEST Samuel Thibault wrote:
> On the long run, it really should. Just hiding issues is not the way
> forward :)
>
> Also, note that if the performance is so bad, it means something *needs*
> to be fixed, otherwise blind users will get the bad performance, an
Control: reassign -1 libqt5core5a
Control: retitle -1 Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge
negative performance impact, qt accessibility should not always send all
messages
Hello,
Lisandro Damián Nicanor Pérez Meyer, on sam. 02 sept. 2017 11:02:15 -0300,
wrote:
> According to
On 2 September 2017 at 12:11, Alex ARNAUD wrote:
> Le 02/09/2017 à 16:28, Lisandro Damián Nicanor Pérez Meyer a écrit :
>>
>> I'm really open to suggestions. at-spi2-core is being installed by default
>> on
>> standard installations, so we are inflicting a huge performance drawback
>> to
>> most o
Le 02/09/2017 à 16:28, Lisandro Damián Nicanor Pérez Meyer a écrit :
I'm really open to suggestions. at-spi2-core is being installed by default on
standard installations, so we are inflicting a huge performance drawback to
most of our users. On the other hand people needing a11y really need to ge
On sábado, 2 de septiembre de 2017 16:18:16 -03 Sebastian Humenda wrote:
> Hi
>
> Lisandro Damián Nicanor Pérez Meyer schrieb am 02.09.2017, 11:02 -0300:
> >According to [upstream] setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a
> >huge negative performace impact on Qt, so it should not be enable
Hi
Lisandro Damián Nicanor Pérez Meyer schrieb am 02.09.2017, 11:02 -0300:
>According to [upstream] setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a
>huge negative performace impact on Qt, so it should not be enabled by
>default. And, if I understand correctly, this is the current behavior.
>
>Ups
Package: at-spi2-core
Version: 2.24.1-2
Severity: important
According to [upstream] setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a
huge negative performace impact on Qt, so it should not be enabled by
default. And, if I understand correctly, this is the current behavior.
Upstream suggested that
19 matches
Mail list logo
