Oh, yep, with this explaination is more clear. Thank you a lot ^^

Solved, overrode the standard event() and just used event.type() == QEvent::hovermove to get what I needed.

@morte ApplicationWindow { Item { id: banner x: 0; y: 0 width: parent width; height: 50 } Item { id: content width: parent.width anchors { top: banner.bottom bottom: parent.bottom } } }

@wangfys I got exactly the same behavior as you. Although I never used the scene graph before, your example (+ the doc and the Custom Geometry example in Qt's examples) gave me a little crash course in the topic. http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph.html Your example really should work as it seems you did everything as required by the doc. At my side, the lines become visible once I hover the mouse one the exit button. Possibly this is a bug? PS. Again, not being useful, I maybe I could suggest you to change the definition of your points from QVariantList points; to QVector<QPointF> points; Then you can use: const float x = static_cast<float>(points[i].x()); const float y = static_cast<float>(points[i].y()); vertices[i].set(x, y); rather than vertices[i].set(points[i].toPointF().x(), points[i].toPointF().y()); as it saves you a couple of calls to toPointF().

Ok, I have not found a solution but a workaround. I have to open and close the external window before my QML gui is opened. So I do this in my main before the QML engine loads the QML file. Then I pass the necessary information from the external window via pointers to my GUI.

I solved it for now by using a size relative to its parent and calculating a scale from it. Also applying the same scale to the position of the Pathview gives a usable solution, but it requires a few additional calculations. I see how the (617 * 411) resolution occurs. So the Windows width: and height: properties are not sizes in pixels.. Desktop - 1920*1200 or 2560x1440 density 4.2969047380546925 pixelRatio 1 Mobile density 6.5092731829573935 - 1620 x 1080 pixelRatio 2.626672502927989 1620/2.6266... gives 617 1080/2.6266... gives 411

Yep, it works. Thanks :)

No ideas? =(

@RiteshPanchal Ok. Here is a very simplified demo which may help you understand the basics. Once you get familiar with these you can explore other options like StackView or SwipeView which also acts as a container for pages and provides methods for its manipulation. The following example consider Item as root element for the child components. You can change it to Window or whatever and adding its related small changes. //Main window //RootWindow.qml import QtQuick 2.6 import QtQuick.Controls 2.0 import QtQuick.Window 2.1 Window { id: root width: 250 height: 250 property QtObject obj1 property QtObject obj2 signal hideObj(QtObject obj) Component.onCompleted: { root.hideObj.connect(onHideObj) } function onHideObj(obj) { obj.visible = !obj.visible } Row { anchors.top: parent.top Button { text: "One" onClicked: { if(!obj1) { obj1 = Qt.createComponent("Item1.qml").createObject(root); } obj1.visible = true; } } Button { text: "Two" onClicked: { if(!obj2) { obj2 = Qt.createComponent("Item2.qml").createObject(root); } obj2.visible = true; } } } } //Item1.qml import QtQuick 2.6 Item { id: item1 anchors.bottom: parent.bottom anchors.left: parent.left width: 50 height: 50 Rectangle { color: "red" anchors.fill: parent Text { anchors.centerIn: parent text: "Item1" } MouseArea { anchors.fill: parent onClicked: root.hideObj(obj2) } } } //Item2.qml import QtQuick 2.6 Item { id: item2 anchors.bottom: parent.bottom anchors.right: parent.right width: 50 height: 50 Rectangle { color: "green" anchors.fill: parent Text { anchors.centerIn: parent text: "Item2" } MouseArea { anchors.fill: parent onClicked: root.hideObj(obj1) } } } The two buttons here creates and shows 1 item each containing a colored rectangle and a text displayed at the bottom. Then after creating these 2 items, try clicking on each individual colored rectangle, it will hide/show other rectangle. This works by sending a signal to the root window from the child component.

Nevermind. I found the solution. The parenting between the main window and the tool window should not be done with setParent but with setTransientParent. I hope this helps someone someday

@ars1614 Well i think the rule is that only top level windows are shown. If a window has a parent,its not top level. Some of it maybe due to the platform etc. But is a flag if possible would be very nice :)

Thanks everyone

Hi QStackedwidget is also good for a design where you want a mainwindow with "pages"

Hi If you use layouts and put the buttons in one. Then no need for any code to do resize. So using layouts is how you do in Visual Design. Try this : Make new project open the mainwindow UI Place a button in the empty mainwindow. Right click empty spot on form Select the Layout menu (bottom) Select Layout Horizontally

Hi and welcome to devnet, Thanks for sharing ! Looks good !

@oblivioncth said: Ok, its shaping up , super :) "Helps givez me codes". We do help those too but good questions often get better answers. Also its clear that you do try to fix it first yourself, so some holes in c++ is no issue. Cheers

@SGaist Thanks for tips. But anyway, as I see the problem, Inability of Creator to remember window layout is not a bug because I had and have the same problem for all Creator Win and Linux versions that I used during last 8 years. Can you prove that you can open several windows and then switch to another session and after that switch back to first session and get previous windows layout? It is very interesting for me to see that.

@gabor53 good work!

@p3c0 said: Window { flags: Qt.FramelessWindowHint } Thanks it works.

Now brochure in English available. http://www.labcsp.com/

Hi, the Visual Studio compilers are the only option if you are targeting Windows Phone and/or Windows Store Apps. Whether there are C++ bindings/headers for a C# library depends on the provider of that library. Even Microsoft is not 100% consistent. Some items are fully supported (In-App-Purchase), some partially (In-App-Advertising) and some are simply not exposed to C++ at all. You will need to check the documentation yourself unfortunately.

Oops sorry about that. I'll write Qt from now on haha. Thanks for correcting me. Also, thank you for the info. I am looking into it right now!

I fixed it like so: Comment out the default w.show() in my main.cpp. I created a Q_INVOKABLE class method on main window called showAppWindow() that merely does a this->show(). I did the steps to inject my C++ object (called cpp) into my Javascript via the C++ <==> Webkit bridge. In my index.html file, at the bottom before the ending BODY tag, I added this: <script type="text/javascript"> try { if (cpp) { setTimeout('cpp.showAppWindow();',100); } } catch(e){} </script>

You're welcome ! As for marking the thread as solved, you can now use the "Topic Tool" button, it will keep the title clean. Also, while browsing the forum, please consider up-voting answers that helped you, that will make them easier to find for other forum users :)

Thank you for reply. I also used this->setWindowFlags(Qt::WindowStaysOnTopHint); and QMainWindow::showFullScreen(); to stay my confirmation message on top. that was my goal.

@bck25 ,@Frime Thank you all for the replies. I can not set the alpha value as I am using an image as the background. I solved this by moving the opacity to the BorderImage which acts as background of the Window. Window { id : root flags: Qt.FramelessWindowHint visible:true color: "transparent" // This works properly when Aero theme is enabled in Windows BorderImage { visible:true width:root.width height:root.height opacity: 0.8 source: "background.png" } }

@lajtu For Screen it works because width is an Attached Property for it.

Hi Thanks for the detailed answer, now the issue solved

Win7 & Qt 5.4.2 with QtCreator 3.4.1

Great ! I forgot that usual suspect… It's a tricky one… Thanks for sharing ! Since you have it working now, please update the thread title prepending [solved] so other forum users may know a solution has been found :)

Compiled and rebuilt with Qt5.5.0 (beta). Unfortunately, the problem persists.

@Chris-Kawa, you got me wrong i guess, the problem is not stylesheet inheritance, it's about the target widget itself NOT getting the stylesheet, instead that only passing style to children, naming him doesn't affect the result too.

@Cosford I am happy to hear you made it. If I helped in any way - my pleasure.

@Chris-Kawa, i see what you did there! :d thanks, didn't even think about that approach before! very useful!

@emppu How to prevent that a user opens the same window twice? Do I need a flag variable in C++ code or is it easily done in QML? This seems a common workflow (preference window, open/save dialog, etc). I don't want to disable the main window while About window is open. You can do it right itself in QML. Declare component as global property and then check for null before creating that component. property Component component ... MenuItem { ... onTriggered: { if(!component) { component = Qt.createComponent("About.qml"); var about = component.createObject(main); about.show(); } } } In my case main window didn't disable. Did you set any particular Qt::WindowFlags flag ? If I keep an instance of About window as an attribute of main ApplicationWindow, does it occupy the memory since the main window is loaded? If I have many different windows, this is really inefficient. What's the simplest solution? Anything instantiated will occupy memory. To delay that process you use the technique you mentioned or you can use Loader to load them dynamically.