Bug 110858 - [WorkbenchParts] Debugging Java source doesn't activate minimized editor
Summary: [WorkbenchParts] Debugging Java source doesn't activate minimized editor
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-27 14:42 EDT by Brad Reynolds CLA
Modified: 2019-09-06 16:03 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brad Reynolds CLA 2005-09-27 14:42:36 EDT
I normally use two rows of editors in Eclipse, one for my code and the other for
Eclipse code.  If I have the second row minimized when attempting to step
through the code of a minimized editor it does not activate and restore that
editor.  It will still step through the code as I can see the variables changing
in the variables view when pressing F5.  But for a while I thought something was
messed up with my workspace because it didn't seem to be properly stepping
through the code when in reality it was, it was just minimized.
Comment 1 Darin Wright CLA 2005-10-24 12:48:28 EDT
Nick, is there any API to access/manage editors in rows - i.e. when there are 
two rows of editors can we tell or change the minimization, etc?
Comment 2 Nick Edgar CLA 2005-10-25 13:40:07 EDT
Not currently, no.  EditorWorkbook is the underlying implementation class, but
workbooks are not exposed at all in the API.

Showing the view or bringing it to top should de-minimize though.
Comment 3 Darin Wright CLA 2005-11-29 12:37:24 EST
In this case, the editor is already open and we do make a call to IWorkbenchPage.bringToTop(IWorkbenchPart), but this has no effect on the minimization of the editor. Moving to UI for comment.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:03:41 EDT
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.