[program-java] Re: Eclipse Breakpoint Detection Question
- From: "Homme, James" <james.homme@xxxxxxxxxxxx>
- To: "program-java@xxxxxxxxxxxxx" <program-java@xxxxxxxxxxxxx>
- Date: Mon, 21 Feb 2011 11:20:17 -0500
Hi Jim,
I hope to get to that point. My Java and Eclipse learning curve is a little
steep right now, but I will get there. Have no fear.
Thanks.
Jim
Jim Homme,
Usability Services,
Phone: 412-544-1810. Skype: jim.homme
Internal recipients, Read my accessibility blog. Discuss accessibility here.
Accessibility Wiki: Breaking news and accessibility advice
-----Original Message-----
From: program-java-bounce@xxxxxxxxxxxxx
[mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Corbett, James
Sent: Friday, February 18, 2011 3:36 PM
To: 'program-java@xxxxxxxxxxxxx'
Subject: [program-java] Re: Eclipse Breakpoint Detection Question
Jim H:
I can report that while in debug mode and on a break point, the information
displayed on the status bar of Eclipse 3.3 is the same as I previously
reported. I'm using JFW Key + #3 on the num pad.
I certainly can assist you with specifics.
Jim
James M. Corbett
Programmer / Analyst |
Canada Revenue Agency | Agence du revenue du Canada
875 Heron Rd.
Ottawa, On.
K1A0L5
James.Corbett@xxxxxxxxxxxxx
Telephone | Téléphone: (613) 941-1338
Facsimile | Télécopieur: (613) 941-2261
Government of Canada | Gouvernement du Canada
E = MC²
-----Original Message-----
From: program-java-bounce@xxxxxxxxxxxxx
[mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James
Sent: February 18, 2011 15:12
To: program-java@xxxxxxxxxxxxx
Subject: [program-java] Re: Eclipse Breakpoint Detection Question
Hi Jim C,
I honestly don't know. All I know how to do in Java so far is very small, so I
might need help even figuring out if I turned something on and it did what it
was supposed to do. I was hoping you could, or someone could, help me figure
out if those features would help JAWS announce it landed on a break point.
Maybe you already know that from context and don't want to hear the
announcement, though.
Jim
Jim Homme,
Usability Services,
Phone: 412-544-1810. Skype: jim.homme
Internal recipients, Read my accessibility blog. Discuss accessibility here.
Accessibility Wiki: Breaking news and accessibility advice
-----Original Message-----
From: program-java-bounce@xxxxxxxxxxxxx
[mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Corbett, James
Sent: Wednesday, February 16, 2011 2:53 PM
To: 'program-java@xxxxxxxxxxxxx'
Subject: [program-java] Re: Eclipse Breakpoint Detection Question
Jim H.:
Ok, F5 thru F7 moves you about in debug mode and depending on the key will
place you on the next line of execution, and that's where you want to be. So
what's on the Status Bar that would be of interest in this context?
Jim
James M. Corbett
Programmer / Analyst |
Canada Revenue Agency | Agence du revenue du Canada
875 Heron Rd.
Ottawa, On.
K1A0L5
James.Corbett@xxxxxxxxxxxxx
Telephone | Téléphone: (613) 941-1338
Facsimile | Télécopieur: (613) 941-2261
Government of Canada | Gouvernement du Canada
E = MC²
-----Original Message-----
From: program-java-bounce@xxxxxxxxxxxxx
[mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James
Sent: February 16, 2011 14:42
To: program-java@xxxxxxxxxxxxx
Subject: [program-java] Eclipse Breakpoint Detection Question
Hi,
I found this piece of text in the Eclipse Help for the Workbench. Would any of
this help JAWS identify breakpoints when we land on them? I am cautiously
optimistic. By the way, I am almost ready to put up the first beta of the
Eclipse JAWS script set. Stay tuned for news of that coming soon, as long as I
don't detect any more problems. I was ready to submit this afternoon and found
a little glitch. See Eclipse help text below.
Here's what I propose. When you press one of the keys that steps you to an
annotation, JAWS automatically speaks the status line. I may be able to make it
speak the status line for other reasons, too, or possibly the parts of
interest. Any ideas appreciated.
Jim
========== Help Text Below ==========
Configuring accessibility options for textual editors
Workbench User Guide
>
Concepts
>
Accessibility features in Eclipse
Configuring accessibility options for textual editors
Textual editors in Eclipse can be configured to better fit the needs of people
using Accessible Technology such as screen readers and magnifiers. This document
describes the relevant options.
Accessing Annotations
You can navigate to the next annotation by pressing Ctrl+. and to the previous
one by pressing Ctrl+,. Out of the box not all available annotation types
are included in that navigation, for example, breakpoints are not part of it.
Breakpoints and other annotation types can either be enabled via the Next
Annotation toolbar button drop-down menu or by checking Include in
next/previous navigation on the
General > Editors > Text Editors > Annotations
preference page.
Navigating to an annotation moves the text caret to the annotated line, and
displays the annotation text in the status line. The next section explains how
to read the status line under Windows.
Some annotation types, for example warnings and errors, can be accessed by
pressing F2 after having navigated to one of them or setting the caret inside
the annotation.
Windows only
Reading the status line with JAWS
JAWS desktop users press Insert+PageDown to read the Eclipse status line and
JAWS laptop users press Caps Lock+PageDown.
Accessing the Current Line Number
You can get the current line number by pressing Ctrl+L or via Navigate > Go To
Line....
Quick Diff Hover
Like normal hovers can be shown by pressing F2, the quick diff and revision
hovers that appear when hovering over the quick diff ruler on the left can also
be shown by pressing a key sequence. However, out of the box no key sequence is
defined for that. Go to the
General > Keys
preference page to assign a key sequence to the Show Quick Diff Ruler Tooltip
command.
Annotation Hover
Like normal hovers can be shown by pressing F2, the annotation hover that
appears when hovering over the vertical ruler on the left can also be shown by
pressing a key sequence. However, out of the box no key sequence is defined for
that. Go to the
General > Keys
preference page to assign a key sequence to the Show Ruler Annotation Tooltip
command.
Reading Words in the Java Editor
In order to get correct results when letting the screen reader read words in
the Java editor it is recommended to disable Smart caret positioning in Java
names on the Java > Editor preference page.
Reading Java Code in the Java Editor
Some screen readers do not read punctuation by default, however it is useful to
hear punctuation when reading code. When using a Java Editor with a screen
reader, you can do the following:
list of 5 items
* JAWS:
list of 6 items nesting level 1
JAWS reads most punctuation out of the box, however it does not say commas. To
change this:
* Utilities > Configuration Manager
* Set Options > Customize Punctuation...
* Select comma in the list, and change the setting from All to Most
* OK
* File > Save (to save the configuration)
* File > Exit (to exit the JAWS Configuration Manager)
list end nesting level 1
* NVDA:
list of 2 items nesting level 1
* NVDA menu (Insert+n) > Preferences > Voice settings...: enable Speak all
punctuation
* NVDA menu (Insert+n) > Save configuration
list end nesting level 1
* Orca:
list of 2 items nesting level 1
* Preferences > Speech > Punctuation level: All
* OK
list end nesting level 1
* VoiceOver:
list of 3 items nesting level 1
VoiceOver reads most punctuation out of the box, however it does not say
commas. To change this:
* VoiceOver Utility
* Verbosity tab
* Punctuation: All
list end nesting level 1
* Window-Eyes:
list of 3 items nesting level 1
* Global > Menu level: Advanced
* Screen > Punctuation: enable Textual, Math, and Miscellaneous
* File > Save
list end nesting level 1
list end
Related tasks
Accessibility features in Eclipse
Navigating the user interface by using the keyboard
Related references
Accessibility preference page
Keys
Font and color settings in Eclipse
________________________________
This e-mail and any attachments to it are confidential and are intended solely
for use of the individual or entity to whom they are addressed. If you have
received this e-mail in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this e-mail without the author's prior permission.
The views expressed in this e-mail message do not necessarily represent the
views of Highmark Inc., its subsidiaries, or affiliates.
Other related posts:
