Re: [orca-list] mate gtk3 version and orca

[Joanmarie Diggs <jdiggs igalia com>]

Hi Kendell.

What you're looking for is:

1. keyboardevents (what you pressed and released). Search for
   "KEYBOARDEVENT". Type of "0" means pressed; Type of "1" means
   released. You'll also have the event_string for the key itself.
2. events that get received (they start with things like "object:"
   and "window:" and "document:")
3. how Orca processed those events. If it spoke something, you will
   see "SPEECH OUTPUT".

A good way for you to tackle what you stated is to compare two very
similar tasks. For instance, if Alt+Tabbing works with Orca in MATE for
Gtk+ 2 and doesn't work for Orca in Gtk+ 3, capture a debug.out from
each and compare by searching for the three things I stated above:

Start with the file captured from where things work as expected:

1. Find the keyboard event where you pressed Alt and Tab by searching
   for KEYBOARDEVENT with a type of "0" and an event_string which has
   the word "tab" in it. You may find it helpful to delete the text
   before this point (copy your file first, of course)
2. Find the SPEECH OUTPUT line where Orca spoke what you expected.
   You may find it helpful to delete the text after this point.

What you care most about is what event caused the SPEECH OUTPUT line.
Find. This. Line. <smiles>

Having done the above with the good output file, do it with the bad one:

1. Find the KEYBOARDEVENT (if we didn't get one, there's the problem)
2. Start reading the events which follow. Since you're trying to find
   out what broke, you'll probably not find a SPEECH OUTPUT line in
   the bad one. Thus what you're looking for is what Orca did not get.

Again, while this process is tedious and boring, all it boils down to is
reading and comparing.

--joanie

On 10/17/2015 06:24 AM, kendell clark wrote:
> hi all
> This weekend I'm going to primarily focus on two things. Fixing whatever
> issue is keeping sonar mate images from booting to the desktop and
> working on getting accessibility bugs filed against mate's gtk3 version
> so they can start being worked on, since mate is moving towards a gtk3
> port. Joanie, if I produce a debug log, would you be willing to help me
> go through it and tell me what events orca isn't being presented with?
> I'd also like to learn what orca is looking for when reading the screen
> so I can pick these events out myself and won't have to keep asking for
> your help since I know you're busy. Would you be willing to give me a
> rundown of what to look for when I'm looking over debug logs? I'll of
> course send the debug logs to you privately so it doesn't trigger the
> moderator. I'm going to do the same for cinnamon, but I'll wait until
> I've learned at least a basic level of understanding of debug logs so I
> can pick out the events myself.
> Thanks
> Kendell clark
>
> _______________________________________________
> 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