Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 18763 - Search for references in workspace twice in a row messes up views
Summary: Search for references in workspace twice in a row messes up views
Status: RESOLVED DUPLICATE of bug 18929
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC All
: P1 critical (vote)
Target Milestone: 2.0 F3   Edit
Assignee: Eduardo Pereira CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-03 11:34 EDT by Curtis d'Entremont CLA
Modified: 2002-06-06 09:33 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 Curtis d'Entremont CLA 2002-06-03 11:34:46 EDT
Build F2 (20020602)
Win2K, Motif, and GTK2

Try this in windows:

1. Open java perspective
2. Create new java project
3. Create new class called "C"
4. Paste the following code in it and then save & compile
--------------------------
public class C {
   static int test;
   public static void main(String[] args) {
      test++;
   }
}
--------------------------
5. Highlight the first "test"
6. Right-click on it, Search->References->Workspace
7. Close search view
8. repeat #6 (search again)

Now the search results don't come up. Instead, the task view looks messed up. 
Try double clicking on the Task view.. all the views disappear!

The same happens in Motif, but in GTK2, an error message comes up 
saying "Unable to create view part".
Comment 1 Erich Gamma CLA 2002-06-04 15:02:38 EDT
double clicking task view zooms into so this is expected.

>Now the search results don't come up. Instead, the task view looks messed up. 
looks like the same symptoms as 18642. Moving to Platform UI
Comment 2 Nick Edgar CLA 2002-06-05 12:25:37 EDT
CCing McQ for the GTK difference.

Eduardo, can you confirm this is a dup of 18642?
Comment 3 Eduardo Pereira CLA 2002-06-06 09:33:44 EDT

*** This bug has been marked as a duplicate of 18929 ***