work around change in 24h2 forcing ws_ex_windowedge on 3.1 windows #1469
+31
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This workaround isn't good enough for battle chess which doesn't work maximized because the border is still 1 pixel too wide. |
|
The client area is the correct size now so battle chess works properly. The border is white on the right and bottom so it doesn't look quite right but the fix that would probably require drawing the border directly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #1468
Using ws_ex_staticedge doesn't look quite right but it doesn't shrink the window. This should also affect win32 nt 3.1 programs so since it's not dead code like the wow stuff maybe it'll be fixed in the future.