This is probably a bug in the documentation, to select which display the window goes to you have to use the macro SDL_WINDOWPOS_UNDEFINED_DISPLAY(0) or SDL_WINDOWPOS_UNDEFINED_DISPLAY(1) when specifying the x,y coords. Let me know if that works for you.

It doesn't change anything. The window goes fullscreen wherever the cursor is.

But I assume that (at least from your tests in a separate bug) testrendercopyex correctly honors the display you ask it to place itself in, is that right?

Not always:
"Starting on screen 1, it sometimes changes to resolution of screen 0 and not the resolution of screen 1. The window randomly shows either at screen 0 or screen 1."

It would be great if we could narrow down the "random" part...there's probably something timing sensitive...

If you restrict yourself to the desktop resolution (no mode changes), does the same issue occur (full screen monitor is selected at random) ?

I use KDE in my system and I don't see these sort of problems you and other users report frequently, do you have a simple way to try this on the same system but with a different window manager?
I keep thinking we will have to eventually incorporate a bunch of wm tailored workarounds, or accept that these reports will keep popping up from time to time.

I tried hard to find out the randomness but have not succeeded, yet.

When using the desktop resolution of screen 0 and set the display argument to 0, the window always opens at screen 0 but tries to resize screen 1 (I get the message "Window requested size 1440x900, got 1600x900" so I guess my 1920x1080 screen is resized to 1600x900). With --display set to 1, it always starts at the screen where the mouse cursor is at with the resolution of that screen.

When using the desktop resolutions of screen 1 and set the display argument to 0, the window always opens at the screen where the mouse cursor is at. With --display set to 1, it always starts at screen 0 at wrong positions (moved up or moved left).

I'm affraid that this information is pretty much useless because it looks like multiple bugs at once and I'm not really helpfull with this all.

Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.