History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEADEV-2610
Type: Usability Problem Usability Problem
Status: Open Open
Priority: Normal Normal
Assignee: Maxim Shafirov
Reporter: AlexL
Votes: 1
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
IDEA: Development

IDEA Find Usages and Find in Path should make best effor to jump to source for INVALID items

Created: 25 Sep 05 00:31   Updated: 06 Nov 08 23:35
Component/s: Code Navigation
Fix Version/s: Undefined

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: None
Image Attachments:

1. idea3496_INVALID_line_items_cannot_jump_to_source.gif
(28 kb)
Environment: Windows XP SP2

Build: 3,496
Severity: Medium


 Description  « Hide
Often I will perform a Find Usages or Find in Path to find some method / code / etc.
with the intent to change it to something else.

As I step through each find result line item, I jump to source and then modify the code.
Now once I change that line, the Find Results window marks the item as INVALID.

Often, when I go to the next item to modify it, I want to go back and copy what I had added
to one of the previous items.

But since the previous items are INVALID, I can no longer jump to source by clicking on the
item.

What I would like to see is that IDEA continue to mark the items as INVALID, but go ahead and
make a best effor to jump to the source code line. The simpliest implementation is to just jump
to the original line number when the search was done.

If you look at my screenshot you can see that even for the INVALID items, IDEA still remembers the
file, line number, and column number of the item.

I understand that if I added or deleted lines, then the jump to source might be off, but I can understand
that, and IDEA has given me adequate warning by marking it as INVALID. To be more exact, IDEA
could modify the line description to remove the column number and indicate the line number is only
approximate, e.g. Change

INVALID (1081, 52) out.println(columns[i].getPaddingTag()

to

INVALID (1081?) out.println(columns[i].getPaddingTag()

Only if the file no longer exists should IDEA do nothing when you click on the item.



 All   Comments   Work Log   Change History      Sort Order:
Sascha Weinreuter - 26 Sep 05 14:29
I agree, I've come across that 'problem' as well. It would indeed be great to be still able to navigate to the location the invalidated element originally was at.