| Summary: | NPE when minimizing a view that's previously been detached | ||
|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Remy Suen <remy.suen> |
| Component: | UI | Assignee: | Project Inbox <e4.ui-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Eric Moffatt <emoffatt> |
| Severity: | normal | ||
| Priority: | P3 | CC: | susan |
| Version: | 1.0 | ||
| Target Milestone: | 1.0 RC2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Remy Suen
Simpler steps as follows: 1. Open a file. 2. Detach the 'Outline' view. 3. Bring it back to the right of the editor. 4. Minimize the 'Outline' view. 5. Restore the 'Outline' view. 6. An NPE is thrown. I should also note that when you minimize the view, its icon does not show up in the trim. You only get the 'Restore' icon in the trim. This is almost certainly a failure in the DnD system to detect that the drop area is an *Editor Stack* (i.e. it's already a SharedElement itself) and seems to be running into issues hosting a view. changing milestone to a future one Win7, Build id: I20100718-2237 I tried the steps to see where we are on this bug. 1. Open a file. 2. Detach the 'Outline' view. 3. Bring it back to the right of the editor. 4. Minimize the 'Outline' view. 5. Restore the 'Outline' view. 6. An NPE is thrown. I don't see an NPE when restoring the outline view in step 6. However when I minimize the outline view in step 4, it behaves as a fast view...it floats on top of the upper right quadrant of the editor. (In reply to comment #5) > Win7, Build id: I20100718-2237 > > I tried the steps to see where we are on this bug. > > 1. Open a file. > 2. Detach the 'Outline' view. > 3. Bring it back to the right of the editor. > 4. Minimize the 'Outline' view. > 5. Restore the 'Outline' view. > 6. An NPE is thrown. > > I don't see an NPE when restoring the outline view in step 6. > However when I minimize the outline view in step 4, it behaves as a fast > view...it floats on top of the upper right quadrant of the editor. I think this latter problem is already described in bug 315807. So I think this bug is fixed and that one is not. (But I'll let Remy say for sure). (In reply to comment #6) > I think this latter problem is already described in bug 315807. Yes, that's the "eager" activation bug. > So I think this bug is fixed and that one is not. > (But I'll let Remy say for sure). Cannot reproduce anymore, marking as WORKSFORME. changing milestone (since we noticed it working in RC2) |