Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359047 - E4 can start on a non-existant monitor making it impossible to work
Summary: E4 can start on a non-existant monitor making it impossible to work
Status: CLOSED DUPLICATE of bug 358627
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-27 08:20 EDT by Dean Roberts CLA
Modified: 2011-09-27 08:22 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 Dean Roberts CLA 2011-09-27 08:20:51 EDT
This is a multi-monitor bug.

I believe these are the steps.  I don't have my 2nd monitor right now so I can not verify but.

1) Open E4 and move it to the 2nd monitor
2) Close and save E4
3) Remove 2nd monitor
4) Start E4

Note that you can see it open towards the non-existant monitor.  You get the icon on the task bar and you know the app is visible on the monitor that you do do not have.

This is NOT simply the cases that the monitor is off/disconnected and Windows thinks it is still there.  Windows knows there is only one monitor currently in use.

This is not an uncommon scenerio.  This would happen for any laptop user that has a docking station with multiple monitors connected.

In the docking station, 2 monitors.  Out of the docking station, 1 monitor.

I almost want to make severity Critical ...  I think the only way I can recover from this is to get a 2nd monitor attached now.  In XP there where keyboard keys where you could force the window to maximize and move it ... I can't seem to figure that out in 7.
Comment 1 Remy Suen CLA 2011-09-27 08:22:35 EDT
You could probably workaround the problem by deleting your deltas file.

*** This bug has been marked as a duplicate of bug 358627 ***