Bug 3840 - [Viewers] free expansion of jar happening when deleting projects (1GEV2FL)
Summary: [Viewers] free expansion of jar happening when deleting projects (1GEV2FL)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P2 critical (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Nick Edgar CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 4008 5771 9113 15434 18535 19509 22512 22801 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-10 23:01 EDT by Greg Adams CLA
Modified: 2003-02-10 07:38 EST (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Adams CLA 2001-10-10 23:01:44 EDT
--- setup --
*	In java perspective
*	Create two java projects
		JavaProject1
		JavaProject2
*	Inside JavaProject1  create two classes in default package
				Class1
				Class2
*	Create package1
*	Create package2

*	Inside package1 create Class3
*	Inside package2 create Class4

You should now have
	JavaProject1
		(Default package)	
			Class1
			Class2
		package1
			Class3
		package2
			Class4
	JavaProject2

-- causing the problem
Select class1 and class2 (have both selected)
Hit Del
Hit enter

BUG
	* Typically the jar in project 1 will suddenly expand

NOTES:
GDA (6/5/01 2:52:45 PM)
	If the jar does not expand try create class1 & 2 and try again.
	Sometimes deleting the remaining classes one at a time, then the remaining packages
	will do it.

EG (6/5/2001 9:11:14 AM)
	not critical
Comment 1 Martin Aeschlimann CLA 2001-10-16 11:13:57 EDT
moved to 'active'
Comment 2 DJ Houghton CLA 2001-10-24 07:22:14 EDT
PRODUCT VERSION:
119 jre win98

Comment 3 Erich Gamma CLA 2001-11-10 13:16:01 EST
This is the JFace refresh behaviour.
When an item was expanded, gets deleted and replaced by
another  one (which isn't expanded) then the expansion state
is changed. This is rare scenario but when it happens it is very
annoying.

Moving to Platform UI 
Comment 4 Kevin Haaland CLA 2002-01-24 21:07:13 EST
*** Bug 4008 has been marked as a duplicate of this bug. ***
Comment 5 Erich Gamma CLA 2002-02-05 14:50:40 EST
*** Bug 9113 has been marked as a duplicate of this bug. ***
Comment 6 Nick Edgar CLA 2002-03-28 13:32:05 EST
While this is annoying, it's not a P1.
Bumped down to P2.
Comment 7 Nick Edgar CLA 2002-05-14 10:00:31 EDT
*** Bug 15434 has been marked as a duplicate of this bug. ***
Comment 8 Nick Edgar CLA 2002-06-01 12:31:04 EDT
*** Bug 18535 has been marked as a duplicate of this bug. ***
Comment 9 Erich Gamma CLA 2002-06-07 14:45:07 EDT
*** Bug 19509 has been marked as a duplicate of this bug. ***
Comment 10 Nick Edgar CLA 2002-07-22 10:46:02 EDT
*** Bug 5771 has been marked as a duplicate of this bug. ***
Comment 11 Knut Radloff CLA 2002-09-04 14:23:56 EDT
*** Bug 22801 has been marked as a duplicate of this bug. ***
Comment 12 Nick Edgar CLA 2002-11-12 01:45:31 EST
Fixed in I20021112.
Comment 13 Knut Radloff CLA 2002-11-14 10:37:09 EST
Verified that the JAR expand problem is fixed. However, a similar problem still 
exists in 20021114.
Create the following structure:

JavaProject
  [default package]   (expanded)
     Class1.java  
  package1            (collapsed)
     Class2.java
 
Collapse package1, expand the default package.
Delete Class1.java or the default package itself. Default package is removed 
and package1 is expanded. Still annoying.
Comment 14 Nick Edgar CLA 2002-11-14 15:18:06 EST
Turns out that setExpanded(false) of an item has no effect if the item has no 
children.  I was calling setExpanded before updatePlus, which adds a dummy 
child item to get the plus (if the content provider says that the element can 
be expanded).  Changed it around to call setExpanded after updatePlus which 
fixes the problem.

Filed bug 26410 against SWT for the setExpanded strangeness.
Comment 15 Nick Edgar CLA 2002-11-14 22:36:48 EST
Fix was released for today's build.
Need to write test cases.
Comment 16 Nick Edgar CLA 2002-12-04 14:36:40 EST
Test case has been added.
Comment 17 Nick Edgar CLA 2003-01-20 15:31:17 EST
Reopened due to bug 29072.  See it for more details.
Also commented out the test case, which will have to be undone when this fix 
is re-released.
Comment 18 Nick Edgar CLA 2003-01-27 16:23:53 EST
Re-released fix.  See bug 29072.
Comment 19 Nick Edgar CLA 2003-02-10 07:38:19 EST
*** Bug 22512 has been marked as a duplicate of this bug. ***