[orca-list] Braille WAS Re: A question for a traceback error message prewenting related

[Tami Kinney <tamara 8024 comcast net>]

Sorry to hijack the topic, but this is a question I've been wanting to 
ask for a while now:

How many of you who work with configuration files and terminal commands 
and other deep down and dirty stuff use braille vs. how many use speech 
only to read the code?

I'm stuck with speech only for the present and into the future, so I 
read these more advanced discussions so that I can get a glimmer of what 
I need to know to advance as a Linux/Orca user...  I'm beginning to 
build up a mental map of how all the layers of accessibility work 
together and recognize more and more of the underlying bits and pieces. 
However, hearing Orca read the directory paths and file names alone -- 
before I could get to read or work with those files -- gives me only 
that: A glimmer. The same goes for reading similar material for my 
projects and other things I actually need to do. /smile/ When I really 
need to, I can work out abbreviations and leters and syntax, but... The 
time factor there is problematic.

I live in Oregon, which means that when it comes to procuring anything 
so useful as a braille display, I am on my own. Over the past 6 or 7 
years, I have not yet run across a programmer who doesn't use braille, 
but... If others are using speech only for programming and other such 
tasks, then maybe I can keep plugging away and learn how to do it, too. 
This would bring me closer to earning money to buy a braille display! /lol/

Thanks!We will now return to our regularly scheduled programming...

Tami

On 11/01/2011 03:27 AM, Hammer Attila wrote:
> Hy Joanie,
>
> Thank you your answer, I think I understand with you wrote. Look
> detailed what can I doing for example the bug 651206 related fix:
> For example, the contraction error related fix I defined following
> setting in src/orca/settings.py file:
> "showcursorComputerBraille",
> #Present the cursor positioned word withcomputer braille format
> showcursorComputerBraille = True
>
> In orca-setup.ui file I created a check box in braille page with I named
> showcursorComputerBrailleCheckButton, and use following general signal
> when the check button is toggled: checkButtonToggled
>
> In orca_gui_prefs.py file the checkButtonToggled function I putted
> following code:
> self.get_widget("showcursorComputerBrailleCheckButton").set_active( \
> prefs["showcursorComputerBraille"])
>
> In _initGUIState(self) function I putted following code line, I think
> this is the matter this situation, I forgotted the try block defining,
> or an if statement defining:
>
> self.get_widget("showcursorComputerBrailleCheckButton").set_active( \
> prefs["showcursorComputerBraille"])
>
> This situation what the better method:
> 1. Doing a try block, and exexute the prewious line.
> In exception part if happening the KeyError exception, simple execute
> the set_active method with False value.
>
> 2. Doing an if statement with ask the settings.showcursorComputerBraille
> setting, and depending the setting value simple execute the set_widget
> method with proper value?
>
> For example, in braille verbosity level only have if statements:
> if prefs["brailleVerbosityLevel"] == settings.VERBOSITY_LEVEL_BRIEF:
> self.get_widget("brailleBriefButton").set_active(True)
> else:
> self.get_widget("brailleVerboseButton").set_active(True)
>
> If you tell me what method prefer this situation in Orca codes, I doing
> the final modifications and attaching the second two functions related
> with the hopefuly final patches.
>
> Attila
> _______________________________________________
> orca-list mailing list
> orca-list 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