Omg, I've just ORed the flags, and now it works as intended.
In QtWidgets it should be:

// To set the window minimized setWindowState(windowState() & ~Qt::WindowActive | Qt::WindowMinimized); // To restore the window from minimized state setWindowState(windowState() & ~Qt::WindowMinimized | Qt::WindowActive);

So in QML it should work in the same way.

great! That works. With that I can spare the toggle functions at all.
Thanks!

Hi,

To add to @kshegunov, you might be interested by the Extending Qt Applications part of the Plugin HowTo in Qt's documentation.

Thanks Chris for the singleShot timer idea. In the meanwhile, I've posted a bug report: https://bugreports.qt.io/browse/QTBUG-54421.

This is what I did. Later I discovered that the problem was that the height of the parent relied on the cildren rect, which is somehow buggy. Thank you for clearifying this.

@vishnu

I have a right-arrow button on my footer where i am pushing a qml file upon clicking. when it is loaded how to disable this button on the footer?

enabled = false on click

How can make a check before pushing If that is alread in the stack i don't the push it?

2 ways.

var myItem = stackView.push( { item: Qt.resolvedUrl("DetailedView.qml"), destroyOnPop:false } ); //check myItem and store it somewhere if(myItem) { } var myItem = stackView.push( { item: Qt.resolvedUrl("DetailedView.qml"), destroyOnPop:false } ); var comp=stackView.get(myItem.Stack.index); //need the item to get its index and not just Stack.index

In case anyone else has this problem, adding this to the RowLayout does the trick:

Rectangle { height: rowLayout.childrenRect.height }

The Rectangle by default has 0 width, and the RowLayout's childrenRect.height property has the value we're after, i.e. the maximum height of its children, visible or not. Bit of a hack, obviously.

@vishnucool220 A little bit on explanation would be helpful alongside just downvoting.

Hi @Jean,

yes, you're right. But in my case this is unfortunately not possible. What I am doing is developing a Toolkit with a bunch of Controls for displaying data. These controls are not used by me (even not used by really developers) but used by people who are configuring the UI pages via drag and drop in the Quick Designer. This is why the logic should be encapsulated within the control...

Thanks again!

Cheers,
Frime