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 3097 - SDL_SetWindowFullscreen does not show whole renderer
Summary: SDL_SetWindowFullscreen does not show whole renderer
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.2
Hardware: x86 Linux
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-18 19:42 UTC by marlborometal
Modified: 2018-08-06 21:20 UTC (History)
0 users

See Also:


Attachments
Differences between aspect ratios (119.90 KB, image/png)
2015-08-18 19:42 UTC, marlborometal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description marlborometal 2015-08-18 19:42:23 UTC
Created attachment 2246 [details]
Differences between aspect ratios

I am using a 32 bit Ubuntu 14.04 LTS with the "Gallium 0.4 on NVD9" graphics thing (over Gnome shell). My screen is an 16:9 Asus monitor.

In SDL2, when using either SDL_WINDOW_FULLSCREEN or SDL_WINDOW_FULLSCREEN_DESKTOP in a 16:9 resolution the whole rendering area is not seen (it seems to be missing the "top" and "bottom" parts). Ocasionally the shift will cause only a very small part (the bottom left) to be seen but this may be my fault for forcing changes many times per second when testing.

I can confirm this happening every single time I try it. I can also confirm that when switching my to any 4:3 aspect ratio everything works out ok.

I am attaching an image with four shots in 4:3 and 16:9, both windowed and fullscreen. I drew a line with SDL from corner to corner, notice the line is cut. Also, notice that the whole "game" is not seen (the right part is cut).

I can confirm this also happening in a small netbook (also with 16:9 ratio).
Comment 1 Ryan C. Gordon 2018-08-06 21:20:21 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.