Community
Participate
Working Groups
--- 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
moved to 'active'
PRODUCT VERSION: 119 jre win98
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
*** Bug 4008 has been marked as a duplicate of this bug. ***
*** Bug 9113 has been marked as a duplicate of this bug. ***
While this is annoying, it's not a P1. Bumped down to P2.
*** Bug 15434 has been marked as a duplicate of this bug. ***
*** Bug 18535 has been marked as a duplicate of this bug. ***
*** Bug 19509 has been marked as a duplicate of this bug. ***
*** Bug 5771 has been marked as a duplicate of this bug. ***
*** Bug 22801 has been marked as a duplicate of this bug. ***
Fixed in I20021112.
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.
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.
Fix was released for today's build. Need to write test cases.
Test case has been added.
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.
Re-released fix. See bug 29072.
*** Bug 22512 has been marked as a duplicate of this bug. ***