Bug 212358 - [Trim] Need window pining ability for top-level windows
Summary: [Trim] Need window pining ability for top-level windows
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows Vista
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-09 19:15 EST by Hacking Bear CLA
Modified: 2013-06-05 10:42 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 Hacking Bear CLA 2007-12-09 19:15:31 EST
Build ID: 3.3.0

Steps To Reproduce:
1. start eclipse
2. create a new window with Window | New Window
3. click on the close window controls to close eclipse
4. Start eclipse again, only the last close window appears

Now repeat the same thing again but change step (30 to exit by File | Exit.

This is correct behaviors in most cases; however, users normally just close windows and don't bother to use the File | Exit. I want a window for which I have spent time configure and arrange to a certain view stay open the next time I run Eclipse even if I accidentally close the windows using the border controls.

So we need some kind of "pinning" ability. Like a pin check box near the window border control. If the control is checked, then even if the window is closed, it will be re-opened next time Eclipse starts; also the closed window can be shown in a list under Window menu in the same eclipse session so that one can also restored easily.





More information:
Comment 1 Eric Moffatt CLA 2007-12-12 10:38:10 EST
This has been the workbench behavior for some time; changing it will, I think, need a stronger push than this one scenario (hint: get some votes for this and I'll revisit it...;-). 

BTW, if you forget to use File->Exit, what's preventing you from forgetting to use the 'pin' affordance (had we supplied one)? Just pointing out that the actual fix is a bit more complicated than just adding some sort of 'pin' hook.

Rather than marking this as WONTFIX I'll place it in the 4.0 bucket to act as a design scenario...I find the current behavior somewhat odd myself.
Comment 2 Hacking Bear CLA 2007-12-15 15:45:59 EST
(In reply to comment #1)
> BTW, if you forget to use File->Exit, what's preventing you from forgetting to
> use the 'pin' affordance (had we supplied one)? Just pointing out that the
> actual fix is a bit more complicated than just adding some sort of 'pin' hook.
> 
> Rather than marking this as WONTFIX I'll place it in the 4.0 bucket to act as a
> design scenario...I find the current behavior somewhat odd myself.
> 

The key difference is that you just need to remember to pin the window once but you have to remember use File | Exit every time you close -- i.e. window pinning is a persistent preference.

Users nowaday will always conveniently exit any application by closing the window directly.
Comment 3 Paul Webster CLA 2007-12-18 08:54:14 EST
(In reply to comment #1)
> This has been the workbench behavior for some time; changing it will, I think,
> need a stronger push than this one scenario (hint: get some votes for this and
> I'll revisit it...;-). 
> 

Unless this is a well documented, opt-in only feature I don't think that it's viable.  ex, the behaviour is not intuitive.

When I click on the 'X' I'm closing the window, and the last window closes the application.  Like in my IE at home or firefox here, closing the windows one results in the application closing when I close the last window.  Opening firefox again gives me one window.

Most applications work this way, and we would *really* need a strong usecase + several other well known apps as an example so as not to confuse our users.

PW
Comment 4 Dani Megert CLA 2013-06-05 10:42:29 EDT
Removing outdated target milestone.