-
Notifications
You must be signed in to change notification settings - Fork 9
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
Fullscreen #2
Comments
Thanks. I am not into changing Qt sources for just a demo project, but:
|
What exactly is the issue with fullscreen? Please report bugs upstream at https://bugreports.qt-project.org/ |
The issue is doublefold:
I didn't verify it myself, but that's what @Manromen seems to tell. And even if it worked, painting status bar in QML myself is quite a burden Yes, it should be tracked in Qt's JIRA somehow, but.. shall we report it already now when iOS controls are not even started yet? |
Well, reported anyway - https://bugreports.qt-project.org/browse/QTBUG-40600 |
Okay, full screen seems to be possible - https://bugreports.qt-project.org/browse/QTBUG-40600#comment-252252 , but then you need to paint statusbar yourself. Well, for prototyping needs we can have an image with transparent background. |
Hi,
I tried to fix the Fullscreen-Issue with some private-api hacking.
But unfortunately I get:
ASSERT: "m_qioswindow->geometry().size() == bounds" in file qioswindow.mm, line 208
So it seems that the Qt-Team is guarding the view size (maybe to be backwards compatible to iOS 6). I think we depend on the Qt-Framework on that issue.
You can see the try in my fork.
The text was updated successfully, but these errors were encountered: