Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 13617 - [navigation] Next problem doesn't always update status line
Summary: [navigation] Next problem doesn't always update status line
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 9423 (view as bug list)
Depends on: 18316
Blocks:
  Show dependency tree
 
Reported: 2002-04-12 09:07 EDT by Nick Edgar CLA
Modified: 2003-08-19 09:09 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2002-04-12 09:07:35 EDT
Build 20020409

- new Java class Test
- insert method:
public void run() {
}
- replace void with voyd by replacing i with y (cursor should be positions 
after y)
- save (with autobuild on)
- it finds the problem and displays it in the ruler, shows squiggles, and adds 
it to the task list
- however, it is not shown in the status line

- hit Ctrl+E
- it has no effect

- move the cursor outside the squiggle
- hit Ctrl+E again
- now it works and the status line updates

- place the cursor above this line
- hit Ctrl+E
- it repositions on the error, but the status line is blank

The status line should always show the error when Next/Prev Problem is used.
Also, it would be good if it showed the error whenever the cursor entered an 
error range.
Comment 1 Martin Aeschlimann CLA 2002-05-01 06:57:27 EDT
*** Bug 9423 has been marked as a duplicate of this bug. ***
Comment 2 Nick Edgar CLA 2002-05-01 15:13:10 EDT
This is important for accessibility and general usability.
Recommend bumping up priority.
Comment 3 Nick Edgar CLA 2003-02-13 09:52:39 EST
Can this be considered for 2.1?
Thanks
Comment 4 Dani Megert CLA 2003-08-11 10:28:05 EDT
There are two features/bugs described here
a) show problem text when caret is inside problem annotation
b) currently we do not jump to the annotation that encloses the caret since we
assume you don't want to jump to the already existing position.

We can fix this PR by
- implementing a)
- implementing b) i.e. select the annotation which contains the caret as well
- implement both

Comment 5 Dani Megert CLA 2003-08-19 09:09:05 EDT
Fixed next/prev navigation:
- if caret is enclosed then select enclosing annotation
- if there's only one annotation then use this one i.e. don't clear status line

Available in builds > 20030819