Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 39593

Summary:	[Launcher] Splash Screen is not Multi Monitor aware
Product:	[Eclipse Project] Equinox	Reporter:	Dean Roberts <dean.t.roberts>
Component:	Framework	Assignee:	equinox.framework-inbox <equinox.framework-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	aniefer, bokowski, debbie_wilson, eclipse, emoffatt, sewe, tjwatson
Version:	3.3	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Dean Roberts

2003-07-03 07:45:13 EDT

The splash screen always comes up in monitor 1.

1) Start Eclipse.
2) Move Workbench window to 2nd monitor
3) Exit Eclipse
4) Restart Eclipse

Note that splash screen comes up in monitor 1.  (Workbench correctly opens in 
monitor 2)

Comment 1 Boris Bokowski

2006-04-13 16:16:11 EDT

Eric, is this still an issue in 3.2?

Comment 2 Boris Bokowski

2007-01-02 11:15:12 EST

Reassigning bugs to reflect changes in ownership.

Comment 3 Kim Horne

2007-06-20 13:55:22 EDT

We dont control where the splash screen is created.  Passing to runtime for fixing or closure.

Comment 4 Andrew Niefer

2008-05-05 10:41:14 EDT

*** Bug 100912 has been marked as a duplicate of this bug. ***

Comment 5 Thomas Watson

2010-04-12 10:35:01 EDT

Closing as wontfix.

Andrew, please correct me if I am wrong, to fix this we would need to persist some state for the splash screen to make it show up on the correct screen where the workbench will be displayed.  I don't think that is possible (aside from the complication of persisting state) because the splash screen comes up before you even choose a workspace, at that point we don't even know where what workspace is going to be chosen or where it will be displayed.

Comment 6 Andrew Niefer

2010-04-12 17:45:04 EDT

Windows opens the splash on the primary monitor.  On GTK we just center the window and GTK figures out what that means.

The launcher don't know the location of the workspace, and has no real place to record its own state information.  I'm fine with closing this won't fix unless someone knows something we don't

Comment 7 Dani Megert

2018-07-24 09:32:18 EDT

*** Bug 537300 has been marked as a duplicate of this bug. ***