Re: [orca-list] Please test master with Gtk+ 3 (re typeahead search and caja event spam)



If you can install orca-git and reproduce the same error you had before, then back out to standard arch package and that issue disappears again I think you will at least have established something in orca-git is causing your issue. All files differing from arch standard orca are then proper suspects until cleared.

On Mon, 26 Dec 2016, Janina Sajka via orca-list wrote:

Date: Mon, 26 Dec 2016 13:22:09
From: Janina Sajka via orca-list <orca-list gnome org>
Reply-To: Janina Sajka <janina rednote net>
To: Joanmarie Diggs <jdiggs igalia com>
Cc: orca-list gnome org
Subject: Re: [orca-list] Please test master with Gtk+ 3 (re typeahead search
    and caja event spam)

Agreed, but unclear how to chase this down. I've been using orca-git for
months without an issue, updating every few weeks or so.


It's a puzzlement.

Janina

Joanmarie Diggs writes:
Hey Janina.

I believe you when you say returning to the official Arch package made
the issue go away. However, I cannot help but wonder if something else
in the orca-git Arch package and/or its dependencies are to blame. After
all, how Orca processes accessible object events doesn't have anything
to do with speech-dispatcher.

--joanie

On 12/26/2016 11:54 AM, Janina Sajka via orca-list wrote:
Hi,

I ran the orca-git script from the Arch AUR repository last Friday by
way of trying out these latest changes. I was surprised by the audio
distortion this introduced. In fact, I found it hard to believe Orca
introduced this noise, as there was an alsa-lib update that got applied
in a general system-wide upgrade.

But, deleting orca-git and returning to the current Orca 3.22.2-1 build
available on Arch alone cleared the noise issue.

I will try again with orca-git, but I can't build at the moment for some
reason or other. It's not fetching the source.

In any case, my main point is that the noise won't be acceptable. Far
better to have too much chatter, imo, if that's the trade-off.

Janina

Joanmarie Diggs writes:
Hi Jean-Philippe.

The other day I removed some more "noise." Have you tested the latest
master? As for not announcing "text" at all, I continue to think that's
a bad idea because you are in the text entry and being in the text entry
means you are not in the icons. Being in the text entry and not in the
icons impacts what keystrokes work and what keystrokes don't work and
what the keystrokes that do work will do.

--joanie


On 12/26/2016 04:10 AM, Jean-Philippe MENGUAL wrote:
Hi,

Do you think we could remove the "noise" in the file manager? Hearing
"text", what we type, the element, makes sense, but the remaining noise
should be missing, don't you think?

Moreover, I know that beginners are disturbed by any "noise", even if
technically it's useful as it says wether we're on a text area or not.
Typically, announcing "text" when typing 1st letters of an icon could
disturb some people.

Couldn't we set this as a preference (in specific prefs for Caja in Orca)?

Thanks for your feedback

Regards,


Le 14/12/2016 ? 14:33, Rapha?l POITEVIN a ?crit :
Hi again,

I made more tests and I've some reflexion:
When the desktop has been just focused, for instance when coming from
the software menu to desktop; if I type one letter, for instance l, it
says "l" "text" and the icon. If I stay on the desktop and I search an
other icon with the same way, it says directly the name of the icon,
which is the behavior I expect.

Is your hack supposed to concern the file manager?

In the file manager, when typing one letter, it says the reached element
and other blabla after. We don't need the other information, but at
least, it says the reached element first which is the most important.

When typing several letters, it says "text", and the letters, and the
element, and the title of the window and other blabla.

Regards,

Rapha?l

On 12/13/2016 06:29 PM, Joanmarie Diggs wrote:
Hey guys.

I just committed a change to Orca master which should minimize some of
the problems described with respect to Caja, which spews accessibility
events rather enthusiastically when typeahead search is used. I have so
far only made the changes for Gtk+ 3 and it is a heuristic. Thus testing
would be appreciated.

Thanks!
--joanie
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org



_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org




--



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]