-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NativeWindow::resizeToScreen()
cause deformated fullscreen
#3241
Labels
Comments
Seems like this is related to the render mode i.e. in CPU rendering, it works, but with Direct mode, it doesn't. Testing here:
We can try to investigate this one... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Description
NativeWindow::resizeToScreen()
call cause deformated fullscreen afterward.It critical when you try to turn AIR application window to fullscreen on specific
Screen
.Reproduced with multiple AIR versions, even with AIR 50.2.4.4, 50.2.4.5, 50.2.5.1 and latest 51.0.1.1 with multiple different Windows devices with different applications.
Same issue in all cases.
Adding timeout after
NativeWindow::resizeToScreen()
didn't help.Didn't test with macOS and Linux.
Related issues:
#3239
#3203
#3177
#3176
#2549
#2497
#2495
#2241
#1840
#1669
#1425
#1200
#1123
#528
Steps to Reproduce
Launch application with code below. It just set stage color to green, draw red rectangle little smaller than fullscreen
Stage
(just to better show issue), resize application window to mainScreen
and change display state to fullscreen.Application example with sources attached.
resizetoscreen_fullscreen_bug.zip
Actual Result:
All stage looks red (without green borders). In real complex applications also you can see that content inside stage deformed (aspect ratio wrong).
Expected Result:
You can see green border at right and bottom. No content deformation.
Known Workarounds
After
NativeWindow::resizeToScreen()
callNativeWindow::maximize()
.See code above.
The text was updated successfully, but these errors were encountered: