We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3105 - Wrong display index when using SDL_WINDOW_FULLSCREEN_DESKTOP
Summary: Wrong display index when using SDL_WINDOW_FULLSCREEN_DESKTOP
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: HG 2.0
Hardware: x86_64 Linux
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-26 12:14 UTC by gogoprog
Modified: 2018-08-06 21:20 UTC (History)
2 users (show)

See Also:

Attachments
Test case code (556 bytes, text/x-c++src)
2015-08-26 12:14 UTC, gogoprog 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description gogoprog 2015-08-26 12:14:07 UTC 
Created attachment 2253 [details]
Test case code

Steps:
1) Create a SDL_Window with SDL_WINDOW_FULLSCREEN_DESKTOP
2) Call SDL_GetWindowDisplayIndex with it
3) Notice that the index is always 0 even when called on a secondary screen

Also SDL_GetWindowSize will be wrong (returning size from desktop #0)
Comment 1 Alex Szpakowski 2015-08-26 14:29:21 UTC 
Can you test using the latest code from Mercurial? I believe various window positioning code has changed since SDL 2.0.3.
Comment 2 gogoprog 2015-08-26 14:56:26 UTC 
I confirm the issue with latest code from Mercurial.
Comment 3 Ryan C. Gordon 2018-08-06 21:20:25 UTC 
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.