Function to set a window's monitor

[SolarLune]

Hello~

I was wondering if it would be possible to add a function to set the monitor a window appears on? That would be helpful for me personally, as I have two monitors and running an Ebiten app always places it directly on my IDE.

[hajimehoshi]

Sure, let me think :-) #1835

[hajimehoshi]

Even with the current Ebiten, you can specify the position by SetWindowPosition. Would this be enough?

[SolarLune]

Unfortunately, no - 0,0 corresponds to the current monitor's top-left corner, so I can't move a window to the left of that (my secondary monitor is to the left of my primary one).

Also, since 0,0 is the monitor's top-left corner, you can't really know which monitor a window currently is on.

[hajimehoshi]

The default position is now not (0, 0) (as of 2.2.0-rc.1). Have you tried?

Also, since 0,0 is the monitor's top-left corner, you can't really know which monitor a window currently is on.

If you know the sizes of the monitor, you can specify the window position, right?

[SolarLune]

I updated to v2.3.0-alpha and 0,0 is still the top-left corner of whichever monitor the window's on. And yeah, knowing the size of the monitors would allow me to work with it.

[hajimehoshi]

Ah yes, (0, 0) is still the top-left corner on Linux. The initial monitor should be the current active monitor but probably this is what you have already indicated: "an Ebiten app always places it directly on my IDE".

And yeah, knowing the size of the monitors would allow me to work with it.

Sure, let me think.

[airtonix]

Related to this is the opposite:

how to know which monitor the window is on?

since ebitten.GetWindowPosition() on linux doesn't return the overall accumulative position it's impossible to answer this question.

if screen one is 1024x768 and screen two is 1920x1080 and as a human i can see the window is on screen two at 300x240, then i expect:

x,y := ebitten.GetWindowPosition() 
fmt.Println(x,y)
# prints 1324, 240

but instead it prints

x,y := ebitten.GetWindowPosition() 
fmt.Println(x,y)
# prints 300, 240

[airtonix]

turns out it does, but it doesn't respect the arrangement defined (by xrandr i think).

[airtonix]

see #2876

[airtonix]

and #2877