Bug 198921 - [refactoring] improve handling of potential matches (show preview, disable by default)
Summary: [refactoring] improve handling of potential matches (show preview, disable by...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 226926 363257 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-08-06 06:58 EDT by Markus Keller CLA
Modified: 2022-12-31 12:52 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2007-08-06 06:58:45 EDT
From bug 192638: If refactorings find potential matches, we show a warning that suggests to review problems on the preview page, but pressing "Continue" does not show the preview page. We should offer a way to show the preview page in theis case, and there should be a filter group for potential matches.
Comment 1 Markus Keller CLA 2011-11-08 11:37:32 EST
*** Bug 226926 has been marked as a duplicate of this bug. ***
Comment 2 Deepak Azad CLA 2011-11-08 23:00:50 EST
(In reply to comment #0)
> From bug 192638: If refactorings find potential matches, we show a warning that
> suggests to review problems on the preview page, but pressing "Continue" does
> not show the preview page. 

It is not possible to see the preview only for rename refactoring because it starts in linked mode. If the refactoring wizard is open for example with Move Refactoring (with snippet from bug 361869) you can see the preview.
Comment 3 Deepak Azad CLA 2011-11-08 23:06:06 EST
*** Bug 363257 has been marked as a duplicate of this bug. ***
Comment 4 Deepak Azad CLA 2011-11-09 00:12:36 EST
Looks like several people, including me, found the warning message a bit confusing/vague (see bug 363257 and bug 361869), hence I guess warning message can also be improved
e.g. "Found potential matches" becomes "Found potential matches for {Java element}"
Comment 5 Eclipse Genie CLA 2018-12-29 01:44:02 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Eclipse Genie CLA 2020-12-19 01:23:14 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 7 Eclipse Genie CLA 2022-12-31 12:52:43 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.