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 1909 - Wrong window placement and OpenGL clipping if text size > 100%
Summary: Wrong window placement and OpenGL clipping if text size > 100%
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: HG 2.0
Hardware: x86_64 Windows 7
: P2 major
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-11 07:25 UTC by Leander
Modified: 2018-08-06 21:20 UTC (History)
0 users

See Also:

Attachments
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 Leander 2013-06-11 07:25:24 UTC 
Setting the text size in Control Panel to other than 100% (e.g. 150%) causes the SDL window to be off center and the OpenGL draw operations to be clipped as well. Almost like coordinates are scaled by the factor.

Not a new issue, has been like this for years.

I'm using SDL_WINDOWPOS_CENTERED_DISPLAY(0) and SDL_GetWindowPosition/Size return the correct values

More info:
32-bit DLLs from hg rev 7290.
ATI Radeon HD 4600 with latest drivers (8.970.100.7000).
Comment 1 Leander 2013-06-11 07:35:21 UTC 
It appears the OpenGL clipping only happens if the window size is large enough.
Maybe when size * scale > resolution?

The wrong window placement always happens.
Comment 2 Ryan C. Gordon 2018-08-06 21:20:20 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.