Re: [orca-list] issues with orca and read only fields

[kendell clark <coffeekingms gmail com>]

hi

I'm not sure, but I can provide a debug log. Would that help? I'm 
somewhat sure there's a carrot, but not completely sure. so if I don't 
have a carrot then it's an audacious issue, not an orca one. I've got to 
get back into the swing of things, I've spent too long in windows and 
forgot about giving good detailed steps. I'll fix that now. I do know 
that pressing f7 doesn't turn on the carrot, which works in libre office 
but not in audacious.

Thanks

Kendell Clark



On 05/26/2017 08:07 AM, Joanmarie Diggs wrote:
> Hey Kendell.
>
> Orca doesn't do anything special in those fields; it just presents the
> new location of the caret as you move the caret. If Orca is having
> trouble, my guess is that you either don't have a caret or Orca isn't
> getting caret moved events. Is there any way you can verify whether or
> not you have a caret?
>
> --joanie
>
> On 05/26/2017 01:41 PM, kendell clark wrote:
> > hi all
> >
> > This is another vague subject line. Orca seems to have trouble
> > navigating by up and down arrow through read only fields, like
> > audacious's lyric area. This is true also of mumble's log area, which is
> > read only. I *think* this means that orca doesn't like gtk3 read only
> > fields, but I'm not positive. It reads pidgin's logs just fine, but
> > pidgin is still gtk2. Can anyone else confirm?
> >
> > 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