Splash screen and loading dialog don't center properly on multiple monitors

[mt-inside]

Steps

• Open fs2client with GUI enabled. You will see the splash screen, followed by a dialog with a progress bar.

Expected

• The two popup dialogs are centered on my primary display

Actual

• The two popups are centered in the middle of all my displays. If I have two screens, this results in a nasty spanning of the central divide.

[conicalflask]

I can see the code that positions the progress box. I'll see if I can chose to position it on the primary display.
The splash may be harder as I think it's out of my control, but I'll investigate.

[conicalflask]

Which os was this on? Each os reports the screen geometry differently apparently.

[mt-inside]

Ubuntu 12.04 / unity. On inspection I'm using the binary nVidia driver's "TwinView" feature, which I believe presents one big framebuffer to X and doesn't give any hint as to the fact that it's two separate monitors (as opposed to proper X xinerama configuration) (iirc). Indeed:
$ xdpyinfo
screen #0:
dimensions: 3840x1200 pixels (1049x331 millimeters)
resolution: 93x92 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
root window id: 0x15d

This may be impossible under such a set-up.

[conicalflask]

Ok. I've had a look and it seems that you can query display geometry in a more fine grained way. (I just ask the default toolkit for the screensize atm.) But it seems that the GraphicsEnvironment exposes more information.

However, if you say you're using twinview then all bets are off as you point out that it appears as one display to applications.

The code here elaborates a bit: http://stackoverflow.com/questions/213266/how-do-i-center-a-jdialog-on-screen

I'll mark this as wontfix unless we can replicate this on Xinerama linux, Os X or Windows.

[mt-inside]

It's worth noting that Ubuntu's unity can see the two monitors, as it knows where to put taskbars and can correctly maximise windows, etc. Who knows how it does it thought, might ioctl the nvidia driver for all I know. I am happy for this to be won'tfix as I'm using binary drivers :)

[slugonamission]

This also happens on Windows 7 IIRC.