Bugzilla – Full Text Bug Listing
| Summary: | [Compatibility] Editor is not shown when asked by the debugger if it is opened in another perspective but not in the shared area | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Hitesh <hsoliwal> | ||||||
| Component: | UI | Assignee: | Remy Suen <remy.suen> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | Remy Suen <remy.suen> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | remy.suen | ||||||
| Version: | 1.0 | ||||||||
| Target Milestone: | 4.1 M3 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 179379 [details]
Screenshot before switch
This could be a difference in where the active editor is placed currently. Switching back to the current perspective reveals the breakpoint.
What are you double-clicking on (from the bug's summary) exactly? (In reply to comment #1) > This could be a difference in where the active editor is placed currently. We're talking about the problem where you have the editor for the file with the breakpoint in question open but it is outside of the shared area _and_ you have the preference to automatically switch to the 'Debug' perspective when a breakpoint is hit and the editor doesn't show up in the 'Debug' perspective, correct? (In reply to comment #3) > (In reply to comment #1) > > This could be a difference in where the active editor is placed currently. > > We're talking about the problem where you have the editor for the file with the > breakpoint in question open but it is outside of the shared area _and_ you have > the preference to automatically switch to the 'Debug' perspective when a > breakpoint is hit and the editor doesn't show up in the 'Debug' perspective, > correct? The point that editor is not being shown and highlighting the breakpoint line after switching to debug perspective is well communicated by the two screen shots. Nonetheless, it makes sense now to share details. Normally, by default, when the debugger hits a breakpoint, the editor is opened (activated) and the corresponding line is highlighted. This can also happen when you *double-click* a stackframe in the *debug view*. The switch to 'Debug Perspective' is *by default* set to *true*. There is prompting, but that is a different point, although most likely to be set to 'Do not prompt again'. If the active editor (target file) happened to be open on a partstack other than the shared one. Then the editor, for some unknown reason, will not show-up in 'Debug Perspective' even after *double-clicking* on a stackframe in the debug view. Please do let me know if would like to have any more details on this. (In reply to comment #4) > The point that editor is not being shown and highlighting the breakpoint line > after switching to debug perspective is well communicated by the two screen > shots. That's what it looked like to me but I like to make sure so I don't fix something that the reporter wasn't actually reporting about. ;) It sounds like we're on the same page though, good. Thread [main] (Suspended (breakpoint at line 540 in WorkbenchPage)) WorkbenchPage.bringToTop(IWorkbenchPart) line: 540 SourceLookupFacility.openEditor(ISourceLookupResult, IWorkbenchPage) line: 270 SourceLookupFacility.display(ISourceLookupResult, IWorkbenchPage) line: 219 DebugUITools.displaySource(ISourceLookupResult, IWorkbenchPage) line: 792 StackFrameSourceDisplayAdapter$SourceDisplayJob.runInUIThread(IProgressMonitor) line: 155 UIJob$1.run() line: 95 Thanks for the bug report, Hitesh. I've committed a workaround for this problem which will be rolled back when implementing bug 325986. Verified on Windows XP with I20101025-1602. |
Created attachment 179378 [details] Screenshot on switch See attached screenshot.