This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

• Xinerama Metamode display (xinerama_metamodes.patch, application/octet-stream, 2012-06-24 09:53:09 +0000, 4642 bytes)

Reported in version: 2.0.0
Reported for operating system, platform: Linux, All

Comments on the original bug report:

On 2012-06-24 09:53:09 +0000, Gabriel Jacobo wrote:

Created attachment 888
Xinerama Metamode display

In a system with two monitors with Xinerama enabled, the attached patch adds a third display that contains the metamode of both monitors combined, with the idea of having a fullscreen window that spans boths monitors. While technically possible, I think this faces window manager issues that I haven't been able to overcome in my setup (Kubuntu 12.04, using the KDE window manager).
I have two monitors:

0 -> Located at 1024,0 with a resolution of 1920x1200
1 -> Located at 0,0 with a resolution of 1024x768

If I create a window this third "meta" display, with a size of say 1920x1200, the window is placed in fullscreen at the origin (0,0)...however, if I exceed that size the window is placed at 1024,0...so creating a fullscreen window of 2944x1200, I get a 2944x1200 window at 1024,0...that is, it exceeds the size of my biggest monitor, but it leaves my left size monitor untouched.

If someone else is able to get this working it would be great, but I think it's the window manager getting in the way. There's literally zero documents online or in the Freedesktop documentation talking about a multimonitor fullscreen window.

On 2013-07-12 22:15:52 +0000, Ryan C. Gordon wrote:

(Sorry if you get a lot of copies of this email, we're touching dozens of bug reports right now.)

Tagging a bunch of bugs as target-2.0.0, Priority 2.

This means we're in the final stretch for an official SDL 2.0.0 release! These are the bugs we really want to fix before shipping if humanly possible.

That being said, we don't promise to fix them because of this tag, we just want to make sure we don't forget to deal with them before we bless a final 2.0.0 release, and generally be organized about what we're aiming to ship.

Hopefully you'll hear more about this bug soon. If you have more information (including "this got fixed at some point, nevermind"), we would love to have you come add more information to the bug report when you have a moment.

Thanks!
--ryan.

On 2013-07-12 22:25:32 +0000, Gabriel Jacobo wrote:

See here for a reference on what this patch requires to be completed: http://forums.libsdl.org/viewtopic.php?t=9195

On 2013-07-26 10:24:35 +0000, Gabriel Jacobo wrote:

Ryan, Sam, I think we can remove this one from the 2.0.0 release, it's an enhancement and it's doubtful it'll work without proper support from the window manager/graphics drivers anyway.

On 2013-07-26 17:17:42 +0000, Ryan C. Gordon wrote:

Removing target-2.0.0 keyword.

On 2018-08-06 21:20:19 +0000, Ryan C. Gordon wrote:

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.