Community
Participate
Working Groups
I20060214-1600 While verifying bug 62218 I noticed that the 3.0 presentation also fails in restoring its tab order. Because the code in the R21 presentation did not change and looks similar to the 3.0 serialization code I think it's a problem in the underlying source. Steps to reproduce: - fresh workspace - create simple project with three files (file1.txt, file2.txt, file3.txt) - open all three files - customize tab order - close workbench - reopen workbench -> tab order is always "file1.txt, file2.txt, file3.txt"
The problem seems to on affect the editor presentation. EditorManager#restoreState tries to restore the state of the editor presentation. During this the presentation is asked to restore its state, i.e. the tab order. This failes because the presentation will get no parts to restore. The EditorStack(PartStack) doesn't have any children. Thus, IPresentationSerializer#getPart(id) returns null for any of the ids to restore. CCing Paul and Doug. It seems that this already popped up for the view tab order (bug 108033).
Does this look familiar, Shaun? PW
Is this still a problem in 3.3? PW
Looks fixed once again in I20060926-0935. Since this problem reappears every once in a while for views and/or editors, I'm sure you already have regression tests for this, don't you?
Changes requested on bug 193523
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
