What about making ApplicationWindow a Item? We could skip the contentItem and there would be designer support.
________________________________ From: [email protected] [[email protected]] on behalf of Tomasz Olszak [[email protected]] Sent: Friday, August 02, 2013 8:49 PM To: Alan Alpert; Bache-Wiig Jens Cc: development Subject: Re: [Development] AplicationWindow, QQuickWindow, contentRotation and setting width and height of contentItem You should also be able to work around it inside your ApplicationWindow by hiding the parent property on your content item. Something like "property Item parent: null" should make it look like the root of the tree. It's not great, but you actually want to pretend to be the root of the tree (it's not just a ModalPopupBehavior hack). Right it solves more issues, but modals are most common. Unfortunately i will not work. When I declared such property I got: Cannot override FINAL property The other workaround that comes to mind is to define your ApplicationWindow in C++ by subclassing QQuickWindow.h and implementing your own contentItem which does include the rotation behavior. I very would like to use ApplicationWindow from QtQuick.Controls module so I would rather not to do that. Would either approach be sufficient for your needs? Because of above, either ApplicationWindow will be moved to C++ or another solution will be found or idea of reusing ApplicationWindow dropped. Didn't you consider such case that certain Item could be declared as quasi root of the tree? Jens correct me if I am wrong but it can be necessary when support of ApplicationWindow styling will be added. -- regards, Tomasz Olszak
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
