This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 131738 - *Find Usages* fails if refresh button is used
Summary: *Find Usages* fails if refresh button is used
Status: RESOLVED WONTFIX
Alias: None
Product: editor
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-01 16:27 UTC by dnikitin
Modified: 2011-03-15 10:25 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dnikitin 2008-04-01 16:27:49 UTC 
Product Version: NetBeans IDE Dev (Build 200803302302)
Java: 1.6.0_05; Java HotSpot(TM) Client VM 10.0-b19
System: Linux version 2.6.20-16-generic running on i386; UTF-8; en_US (nb)
-------------------------------------------------------------------

-- do find usages
-- click refresh button on Usages view
==> Find Usages window appears on the screen
-- click cancel button
-- click refresh button on Usages view again
-- click ok button on Find Usages window
==> [0 occurrences]
Comment 1 Vladimir Voskresensky 2008-04-05 13:20:53 UTC 
I've made some investigations. This is the core refactoring problem, it's not C++ related (try in Java => same result).
The problem is in AbstractRefactoring implementation.
If cancel was set up once to true => then next Refresh always give 0 results, because of 
if (cancel) check in each method before asking plug-ins.

I think "cancel" must be set to "false" when refresh is called.
Comment 2 Jan Becicka 2008-04-07 08:25:59 UTC 
Easy workaround. Invoke Find Usages again. Not P2.
Comment 3 David Strupl 2009-03-31 15:56:45 UTC 
Resolving all issues with milestone "future" as LATER. If you feel strongly that
it should be implemented please reopen and set the target milestone to "next".
Comment 4 Quality Engineering 2009-11-02 11:17:50 UTC 
NetBeans.org Migration: changing resolution from LATER to WONTFIX
Comment 5 soldatov 2011-03-15 10:25:21 UTC 
On elif some test is marked as "Known Failure"