Re: Gedit focus issue (was, Re: Serious accessibility issue in Gnome 2.15.)
Yep and Thanks! I'm surprised there's not a object:state-changed:focused event in the Edgy version. I'm seeing that on my box. :-( Will On Tue, 2006-08-15 at 16:53 -0400, Joanmarie Diggs wrote: > Hi Will. I'll take a stab at it. > > In Dapper: > [...] > window:maximize > object:state-changed:iconified > focus: > object:property-change:accessible-value (8x) > [...] > > In Edgy: > [...] > window:maximize > object:state-changed:iconified > object:property-change:accessible-value (8x) > object:state-changed:showing > object:state-changed:visible > object:state-changed:iconified > [...] > > Is that what you're looking for? > > Take care. > Joanie > > > If someone has some time on their hands they might try seeing if there > > are different event orderings between GNOME 2.14 and GNOME 2.15/16 for > > this gedit maximize/unmaximize scenario. The events of interest > > probably include: "focus:" "window:activate" "window:deactivate" and > > "object:state-changed:focused". > > > -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Gedit focus issue (was, Re: Serious accessibility issue in Gnome 2.15.)
Hi Will. I'll take a stab at it. In Dapper: [...] window:maximize object:state-changed:iconified focus: object:property-change:accessible-value (8x) [...] In Edgy: [...] window:maximize object:state-changed:iconified object:property-change:accessible-value (8x) object:state-changed:showing object:state-changed:visible object:state-changed:iconified [...] Is that what you're looking for? Take care. Joanie > If someone has some time on their hands they might try seeing if there > are different event orderings between GNOME 2.14 and GNOME 2.15/16 for > this gedit maximize/unmaximize scenario. The events of interest > probably include: "focus:" "window:activate" "window:deactivate" and > "object:state-changed:focused". -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Gedit focus issue (was, Re: Serious accessibility issue in Gnome 2.15.)
Hi All: Just to follow up... I'm not sure of the exact cause of the differences here (e.g., metacity, gedit?), but we put a workaround in Orca to handle the differences between GNOME 2.14 and GNOME 2.15/16. Thanks for reporting this problem! If someone has some time on their hands they might try seeing if there are different event orderings between GNOME 2.14 and GNOME 2.15/16 for this gedit maximize/unmaximize scenario. The events of interest probably include: "focus:" "window:activate" "window:deactivate" and "object:state-changed:focused". Will On Wed, 2006-08-09 at 12:46 -0400, Joanmarie Diggs wrote: > Hi all. I just gave this a try. I can confirm Al's findings. And it > seems to occur any time you resize the window (e.g. if it's maximized > and you unmaximize it, the problem also occurs). > > In answer to Will's questions/suggestions: > > > This sounds like a separate problem. Do you have someone that can > > eyeball gedit for you to make sure keyboard focus is really back in the > > gedit text area after you've maximized the window? That is, is the > > cursor really moving when you press the arrow keys? > > Focus is really back in the gedit text area. I arrow around but Orca > says nothing. > > > In addition, once you've maximized the window, can you try pressing F10 > > and then Escape (e.g., bring up an app menu and then dismiss it)? This > > might force a focus event on the gedit window and get the cursor routing > > working again. > > This does get it working again! > > > Finally, did you verify that you don't see the problem on GNOME 2.14 > > using the same exact Orca bits? > > Yep! On my Dapper machine this does not occur. And to be sure I had the > same exact Orca bits, I just built from CVS on each machine. > > Hope this helps! Take care. > Joanie > > -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: RFC: Easier console accessibility configuration.
On Tue, 2006-08-15 at 14:40 +1000, Luke Yelavich wrote: > However, I am wondering about how we may present these options to the > user. Even though speakup is a console tool, users may still wish to > enable it when in GNOME, and they also may wish to enable spoken boot. I > was thinking it may be possible to extend the assistive technologies > control panel somehow, and add a tab with the options available, but I > also think we should have a command-line tool available to > enable/disable/show status as well. > The main trouble here I can forsee is that the option is deep into the running machine and that people with the most limited accessibility will not be able to reach it without help. The option should also be at the very first boot of the CD, along with the other accessibility options, and this should result not only in the Live CD using this but inherently enabling it on the installed system as well. Scott -- Scott James Remnant [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: sudo and accessibility
I had to refresh the gnome-session patch with CVS HEAD, because other patches had been committed in the interim. To fix accessibility for sudo GUI tasks on Ubuntu, then apply the below referenced patches to CVS HEAD versions of at-spi, gnome-session, and gdm. http://bugzilla.gnome.org/show_bug.cgi?id=163132 http://bugzilla.gnome.org/show_bug.cgi?id=345428 http://bugzilla.gnome.org/show_bug.cgi?id=345434 Thanks for helping to test. -- George (gk4) -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 56452] Re: Crashes frequently
-- Crashes frequently https://launchpad.net/bugs/56452 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 56452] Crashes frequently
Public bug reported: 'at-spi_at-spi-registryd' crashes when trying to start an AT application like gnopernicus. See attached crash log ** Affects: at-spi (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Crashes frequently https://launchpad.net/bugs/56452 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
