Summary: | [EditorMgmt] Editor History not updated when SourceLookupFacility reuses an open editor | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Tracy Hodges <tracy.hodges> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | REOPENED --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.1.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Tracy Hodges
2006-07-19 10:17:07 EDT
Using IWorkbenchPage.reuseEditor(...) lead me to this error: Problem detected with part org.eclipse.debug.ui.sourcelookup.CommonSourceNotFoundEditor (class = org.eclipse.debug.ui.sourcelookup.CommonSourceNotFoundEditor): Editor is not firing a PROP_INPUT event in response to IReusableEditor.setInput(...) Fixed in SourceLookupFacility and CommonSourceNotFoundEditor. fixed, pending verification Doesn't seem to be working when you select another frame. The following simple exmaple demonstrates: public class C1 { public void foo() { System.out.println("breakpoint"); //breakpoint here } } public class C2 { public static void main(String[] args) { C1 c1 = new C1(); c1.foo(); } } Run C2 following the steps above, and notice that if you select the stack frame for C2 while suspended at C1, the C2 editor is not added to the MRU editor list. As we are now using the workbench page's method I'll kick it over to them for comment. Punting to Boris Cannot reproduce. WorkbenchPage.reuseEditor() was changed as part of the fix for bug 165970, which might have fixed the issue described here as well. I have retested this myself again using the 3.4 codebase. The problem is still present and easily reproducable. NOTE: You must have the debug preference 'Reuse editor when displaying source code' set to checked. Reopening the issue. 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. |