Community
Participate
Working Groups
There are a number of workflows in the UI where control/focus is passed from a vie w to an editor. For example, selecting a problem in the problems view moves input focus to the editor, highlighting the line in question. There is no easy way to get back though. In the case of the problems view however, a common work flow is select problem -> click to see in editor -> select next problem -> select to see in editor This issue becomes even more apparent if the view in question is a fast view since more work is involved in finding it in the trip and expanding it. What would be good is there was a dedicated key command to get you back to the view that drove focus to the editor. Presently we have a fluid way of moving from view to editor, we also need a corresponding fluid way of moving back. An implementation might be as simple as remembering the last view that had focus.
Nice one...sort of a 'show last view'. Kevin, we should also provide a dedicated (bound) command to toggle the max/restore state of the Editor Area (as opposed to 'Ctrl-M' which toggles the state of the currently active part). Perhaps 'Alt-M' ?
Works for me: Window > Navigation > Next View (Ctrl+F7). Maybe the best fix for this bug would be to move it to Doc and add it to the Platform Tips & Tricks.
There might be a regression in regards to the expected functionality, see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=501443
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. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as wontfix. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
