Re: Ubuntu-accessibility Digest, Vol 66, Issue 9
Hi, MacKenzie, Unfortunately, I don't think we'll be able to do it in 11.10. To make it possible to just flip a screenreader on would require that QT_ACCESSIBILITY environment variable be set to 1 in *all* sessions as a default. With Qt-AT-SPI installed, this'd cause a huge performance impact because Qt-AT-SPI is too new to have been optimised yet. snip I understand. Here's another one for you then: Could a script be used that would insert the needed lines into the configuration file for KDE? Any user who wanted to activate it could run it from a console session. It could have a name like ACTIVATE-SCREENREADER and require root priveleges to be run. The fact that it is written in upper case and that it is a long string along with it's requiring sudo before it is run should preclude any possibility of someone running it accidentally. It would have the benefit of something being there for those who needed it which would automate all the steps necessary for it to get set up while not impacting those who don't in any way other than having a small text file on their system (doesn't have to be long). It would allow for more people to be able to test the screen reader. Just conjecturing. Thanks for having been willing to consider the hotkey feature. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Ubuntu-accessibility Digest, Vol 66, Issue 9
On Thu, May 12, 2011 at 9:40 AM, Alex Midence alex.mide...@gmail.com wrote: Unfortunately, I don't think we'll be able to do it in 11.10. To make it possible to just flip a screenreader on would require that QT_ACCESSIBILITY environment variable be set to 1 in *all* sessions as a default. With Qt-AT-SPI installed, this'd cause a huge performance impact because Qt-AT-SPI is too new to have been optimised yet. snip I understand. Here's another one for you then: Could a script be used that would insert the needed lines into the configuration file for KDE? Any user who wanted to activate it could run it from a console session. It could have a name like ACTIVATE-SCREENREADER and require root priveleges to be run. The fact that it is written in upper case and that it is a long string along with it's requiring sudo before it is run should preclude any possibility of someone running it accidentally. Actually, you wouldn't want it to be sudo, because you don't want your user's KDE config files to be owned by root. A regular script should work fine though. I really doubt anyone's going to accidentally type kscreenreader --enable and have no idea why the computer is talking to them later. There was discussion in the kde-accessibility IRC channel yesterday of integrating it into KAccess (the KControl Module for turning on various accessibility features) as well. Fregl (QAccessiblity developer at Nokia) is at a KDE-and-GNOME-together accessibility hackfest where today they are going to be brainstorming how to make it possible to enable this stuff at runtime, in which case the hotkey thing would then be possible. -- Mackenzie Morgan -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [orca-list] When I doing any Orca laptop binding command, capslock always turned on/off
Yes, I can consistently reproduce this issue! It is, most certainly, a Natty thing, that has not happened in previous Ubuntu versions. Kind Regards, Dave On 05/12/2011 10:25 AM, Hammer Attila wrote: Hy, I see a little disturb problem with my Natty system, with perhaps machine specific: I using Orca with laptop layout. When I press an Orca keystroke, caps lock is always toggling on/off. I think prewious locked the caps lock with off state, and only possible toggling caps lock if the user press Orca+Backspace key and Capslock key. Anybody possible reproduce this issue? How can possible disabling this working method? If I remember right have a xmodmap command with disable Capslock switching. In natty I possible reproducing this issue with Orca 3.0.0 factory packaged version and Orca 3.1.1 master development version. Attila ___ orca-list mailing list orca-l...@gnome.org http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca. The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines Log bugs and feature requests at http://bugzilla.gnome.org Find out how to help at http://live.gnome.org/Orca/HowCanIHelp -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
