Bug 42763 - ctrl-del shift-right arrow stopped working due to error
Summary: ctrl-del shift-right arrow stopped working due to error
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: Douglas Pollock CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-09 05:33 EDT by Oyvind Harboe CLA
Modified: 2003-09-16 17:00 EDT (History)
0 users

See Also:


Attachments
Shows error message (214.29 KB, image/pjpeg)
2003-09-09 05:36 EDT, Oyvind Harboe CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oyvind Harboe CLA 2003-09-09 05:33:53 EDT
I'll attach a picure.
Comment 1 Oyvind Harboe CLA 2003-09-09 05:36:40 EDT
Created attachment 6035 [details]
Shows error message

I was in the process of changing the method in the picture from protected to
public. In doing so I was going to use ctrl-del to delete "protected", but it
had no effect. 

There are no breakpoints set in the project.


When I restarted Eclipse, the "breakpoints" errors in the progress requester
was gone.

Eclipse 3.0 M3
Comment 2 Oyvind Harboe CLA 2003-09-09 05:40:42 EDT
Here is a small reproduceable case:

1) add the following class(with compilation error) to a JDT project

public class Silly
{
asdf
	public static void main(String[] args)
	{
	}
}


2) double click on the red icon. 

3) you should now see the "Progress" view with the "ERROR: Breakpoint location 
validation : Breakpoint cannot be set at the given position".

4) Set the caret at the beginning of the line

5) press ctrl-del, nothing happens. ("asdf" should be deleted).

Comment 3 Douglas Pollock CLA 2003-09-16 17:00:14 EDT
Works for me on Windows XP using I20030916.  Double-click sets breakpoint on the
opening brace.  Ctrl+Del deletes "asdf".  I tried also playing with other types
of breakpoint failures: on the method declaration and on a comment.  Neither one
caused the effects you describe.

However, I could reproduce on 3.0-M3.  I'd recommend upgrading to I20030910 or
I20030916 to fix this problem.

If you still do have a problem, please send more configuration details (Help >
About Eclipse Platform).  Thanks.