Bug 262012 - [FastView] Restore pop-up view
Summary: [FastView] Restore pop-up view
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-22 09:37 EST by Wojtek Bok CLA
Modified: 2019-09-06 15:32 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wojtek Bok CLA 2009-01-22 09:37:19 EST
Build ID: 3.4

Steps To Reproduce:
If I do a search, then the search view pops-up over the editor. So the lower part of the editor and its contents are "under" the search view.

If I click on an item in the search, then an editor is created showing that class. However, sometimes the item I am looking for is located "under" the pop-up search view. The only way I can see it is to have the search view minimize.

But then I do not have access to the next/previous search item buttons as they are in the search view, which is now minimized. I can click on the "restore" button which opens the view "pushing" the editor up. Now all the next/previous items are always showing in the editor.

Is it possible to add a "restore" button to a view which pops-up over the editor?

So in the above scenario, the search view pops-up. I determine that I want to navigate, so I click on the "restore" button which resizes the editor making it entirely visible.

A possible simple way to implement would be to minimize the view, then restore it, mimicking the two button clicks.
Comment 1 Dani Megert CLA 2009-01-22 09:49:45 EST
This is a general issue: once the editor area is maximized, opening a new view results in this view being shown as fast view. Maybe we should just exit maxed mode in this case?
Comment 2 Eric Moffatt CLA 2009-01-26 14:48:39 EST
There are two answers that have come up in other discussions around FV/Search issues...

1) move the Search view to the right side and use vertical orientation. This will make it less likely that it'll obscure the editor.

2) When using this workflow rather than maximizing the editor area, minimize the stacks -except- the stack containing the search view. This will leave you with the largest available editor area with still co-existing with the search view in place...

BTW, there is a 'restore' button on the stack that simply un-maximizes...note also that you can use the built in keybinding (usually F12) to close the search view and activate the editor...
Comment 3 Wojtek Bok CLA 2009-01-26 15:07:38 EST
The search view (or any quick view) will minimize when clicking into the editor area.

I would argue against the right-hand side vertical view as that would mean scrolling right/left to see the results.

I do not mind the quick view obscuring the editor in most cases. I would just like to make it a "view" with one click rather than two clicks. Not just the clicks, but locating the buttons, moving the mouse over, etc. On a 1920x1600 resolution screen, there is quite an area to be traversed.

I will admit that I am ignorant of the inner workings, but it seems to me that implementing this should be as easy as adding the restore button to a quick view. The button would minimize the quick view, then restore it. The minimize and restore actions would be the same as they are now, just that they would be activated under program control rather than by a mouse click.

The quick blink of the view minimizing and restoring would not be an issue for me.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:32:09 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.