Bug 214562

Summary: Main window stuck offscreen in dual monitor Mac config after moving menubar
Product: [Eclipse Project] Platform Reporter: Tom Lane <tlane>
Component: SWTAssignee: Silenio Quarti <Silenio_Quarti>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: cocoakevin, eclipse, steve_northover
Version: 3.3.1   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Attachments:
Description Flags
screen shot none

Description Tom Lane CLA 2008-01-07 20:17:55 EST
Build ID: M20071023-1652

Steps To Reproduce:
1. Set up a Mac with a dual monitor config. I'm using: MacBook Pro 1440x900 screen as the inital menubar screen and an external 1600x1200 screen positioned to the right with the top left corner touching the top right corner of the left screen.
2. Open Eclipse
3. Move the main window to the right monitor and maximize it
4. Close Eclipse
5. Go to System Prefs > Displays > Arrangement and move the menubar to the right monitor
6. Open Eclipse
 
 Actual Results: The window is positioned mostly off to the right of the right screen. Just a couple hundred pixels of the left edge of the window are visible, and crucially the menubar overlaps the window title bar, so you can't move/resize it or click its close button.
 
 Expected Results: At least you should be able to reposition the window. Ideally it would reposition itself appropriately.


More information:
Workaround: Move the menubar back to the left screen, resize and reposition the window so that its title bar is no longer flush with the top of the screen, move the menubar to the right, and then grab the window title bar and move it into view.
Comment 1 Steve Northover CLA 2008-02-27 08:24:26 EST
Kevin, you have a multi-monitor Mac, right?  Can you make this happen?
Comment 2 Kevin Barnes CLA 2008-02-27 18:19:48 EST
Created attachment 90949 [details]
screen shot

yes. Notice Eclipse in top right corner of this screen shot.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:16:55 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.