Community
Participate
Working Groups
I20070524-0010 Using the example program below, use the following steps: 1. Add breakpoint at System.out line 2. Debug 3. Resize Variables view to show about ten lines 4. Arrow down/right/down into the array to about index 15 5. Press the "Collapse All" toolbar button 6. Expand "a" again Expected: plus signs next to the elements of a Actual: No plus signs next to those elements that had been materialized before Happens on the Mac and on Windows. package snip; import java.util.Date; public class J { public static void main(String[] args) { Object[] a = new Object[20]; for (int i = 0; i < a.length; i++) { a[i] = new Date(); } System.out.println("breakpoint here"); } }
Cannot reproduce using a modified version of the snippet from bug 188663 (added a collapseAll button and added a couple more child and grandchild nodes), so my current guess is that this is specific to Debug.
I only see the problem in my host, but not my target.
Ahha - seems to be linked to filter settings which differred in my host/target. The problem only happens if I don't show statics or constants.
I think this is a JFace bug. When the tree is recursively collapsing children, it gets to array entry items, which have dummy children (1 child with null 'data'), since they have never been expanded. The call to #getChildren(widget) for the array entry element returns the dummy element, but has the side effect of causing a #setData callback. This populates the item asynchronously, but in our case the first model object is filtered, so it is removed. This removes the dummy item from the tree, making the plus sign disappear. So, a child is retrieved, but the child count was never updated properly. For the case of a virtual tree, I think the child count should be updated in the case that a dummy child is found/collapsed.
Marking 3.3.1 - I doubt that I will be able to provide a fix that is safe enough for 3.3. Darin, do you agree?
I'm not sure how tricky the fix is... but 3.3.1 is fine with me.
Removing the 3.3.1 target
Hitesh is now responsible for watching bugs in the [Viewers] component area.
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.
