RE: Eclipse: How Do You Find Compiler Error Line?

  • From: "Sina Bahram" <sbahram@xxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Fri, 27 Aug 2010 10:15:39 -0400

Ken, buddy, drink more coffee.

Uhm, that's what I just said.

Once you're in the errors list, hit the applications key, and so on and so 
forth. Some people don't have an applications key, so I
was letting them know they could also route jaws to PC, then hit right mouse 
button.

Take care,
Sina

-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry
Sent: Friday, August 27, 2010 10:01 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Eclipse: How Do You Find Compiler Error Line?

Yuk that's the ugliest way I have ever heard.  I just do control f7 and hold 
shift that brings you into the list of open windows.  I
then pick problems.
That gives you the list of errors and warnings.  You can then select the error 
you want to deal with and use the application key to
bring up all the cool stuff you can do with the error like quick fix or jump to 
etc.

Ken

-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram
Sent: Friday, August 27, 2010 9:54 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Eclipse: How Do You Find Compiler Error Line?

I think I can from memory. I don't have eclipse in front of me.


When you're in the errors list. You can right click on any error. This is done 
by hitting the applications key, routing jaws to pc,
then hitting the right mouse button keystroke, etc, etc. in that context menu, 
you can select "fix" or something along those lines.
This will either fix the error if there's only one solution, possibly after 
asking you whether you want to proceed, or ask you which
fix you'd like Eclipse to apply. Usually it's something easy like adding an 
import, capitalizing a type name, calling a function
with the right number of arguments, and so on.

Take care,
Sina

-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Stanzel, Susan - 
Kansas City, MO
Sent: Friday, August 27, 2010 9:49 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Eclipse: How Do You Find Compiler Error Line?

I know, but could you just write it down? Watching Sina gave me hope.

Susie

-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram
Sent: Friday, August 27, 2010 8:41 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Eclipse: How Do You Find Compiler Error Line?

This is correct. Also, Susie can now tell you about autocorrecting the error 
too. Susie, remember I showed you this feature in
Dallas?

Take care,
Sina

________________________________

From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Stanzel, Susan - 
Kansas City, MO
Sent: Friday, August 27, 2010 7:30 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Eclipse: How Do You Find Compiler Error Line?



WOW, here is Eclipse help I can actually give instead of being on the receiving 
end all the time. Hit control and F 7 and this is
how you cycle through things you need. You need problems. Now some folks use 
alt w v p p and this will also get you to your problem.
Now I am not certain of this, but if you hit enter on the error it will take 
you to the problem code. Anyone else, if this is not
correct please chime in. After yesterday I was totally frustrated, but today 
I'm ready to go on.

 

Susie Stanzel

 

From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James
Sent: Friday, August 27, 2010 6:14 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Eclipse: How Do You Find Compiler Error Line?

 

Hi,

I typed a sample Java program into Eclipse. I put an error in it. When I 
pressed F11, Eclipse asked me if I wanted to open the Debug
perspective. Should I let it do that, or not? And whether I do that or not, 
where do the compiler errors show up, and how do I get
back to my program and figure out which line they are on? 

 

Thanks.

 

Jim

 

Jim Homme,

Usability Services,

Phone: 412-544-1810. Skype: jim.homme

Internal recipients,  Read my accessibility blog 
<http://mysites.highmark.com/personal/lidikki/Blog/default.aspx> . Discuss
accessibility here 
<http://collaborate.highmark.com/COP/technical/accessibility/default.aspx> .
Accessibility Wiki: Breaking news
and accessibility advice
<http://collaborate.highmark.com/COP/technical/accessibility/Accessibility%2
0Wiki/Forms/AllPages.aspx> 

 

 

________________________________

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.


__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

Other related posts:

  1. Home
  2. programmingblind
  3. Archive
  4. 08-2010