Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 Build Identifier: 3.5 CDT 6 included two new view shortcuts for the Debug perspective that were not in CDT 5 (DSF Disassembly and Memory Browser). If I create a new workspace with CDT 6 installed and debug a project, Window -> Show View has the new views. If I open an old workspace and debug a project, the views are missing. I believe the view shortcuts are saved in .metadata/.plugins/org.eclipse.ui.workbench/workbench.xml to implement Customize Perspective - even if you don't customize the perspective explicitly. Perhaps if a list of present views and a list of excluded views were saved we could identify newly added views? Reproducible: Always Steps to Reproduce: 1. Install Eclipse 3.4 / CDT 5 2. Create and debug a project. 3. Open the same workspace in Eclipse 3.5 / CDT 6, with the Memory Browser optional feature installed. 4. Open and debug the project. Observe Window -> Show View is missing the Memory Browser, even though a viewShortcut is present. The shortcut is in org.eclipse.cdt.debug.ui.memory.memorybrowser. The feature is org.eclipse.cdt.debug.ui.memory.
You are in the correct area. The only way to make enhancements to an open perspective (new views, new view shortcuts, new actionSets, etc) visible is to reset the perspective. This is by design. While I wouldn't look at the new view/view stack in the perspective problem (as the open views and their placement in a perspective is user controlled and changes frequently) there is room for enhancements to the shortcuts as the user cannot effect them as easily (unless they've customized the perspective). PW
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.
