Community
Participate
Working Groups
Erich Gamma: "since the editor reuse policy can only be set globally and not per perspective you end up with many open editors in the debug perspective. It can happend that ones your are working one get closed because of the ones opened by the debugger." Would be nice to be able to control editor re-use by perspective.
oops, my words are really hard to understand... 2nd attempt: Since you can only set the editor reuse preference globally and not per perspective you can end up with many open editors in the debug perspective. For example, I've set it to 8. When stepping through code you quickly get to the reuse threshold and as a consequence editors that I was working with can get reused and I have to reopen them. I find myself to often fall back to the old "close all editors" pattern. Pinning can help to avoid that the editors I'm working with are getting closed. However, I often forget to pin an editor. Random ideas - editors that I've changed once during my session should be pinned automatically or should considered specially in the reuse policy. - support to close all editors except the pinned ones. - I can set editor reuse policy per perspective, i.e., for the debug perspective I would set it 1 (giving me the old behaviour).
one option to consider is whether we should fall back to the manual editor reuse policy when opening editors from the debug view. However, I'd like to get more user feedback on this one.
We can now set the editor threshold in the debug perspective to be different that the workbench preference.
Set editor threshold to 1 in the DebugPerspectiveFactory. Works in most cases... Failure: Select a stack frame Hit F3 to open a new type from seleted source (System.out.println()) The PrintStream.class is opened AND the editor for the debug source is also open.
Problem is that the launch view is activated when the "old" editor is closed and the new editor is not yet opened. Is this intentional...seems strange to activate another part when the EditorManager is about to replace the old editor with the new one. Would seem to lead to flash.
Moving to platform UI.
Nick, please confirm that the editor reuse isses raised by the debugger team have been resolved for 2.0
Darin, can this be closed?
Yes, this can be closed. The debugger manages its own editor re-use in the current code base.
Closing.
