@Axel-Spoerl said in A Strange Qt and postgresql problem ! when using Kaspersky:

If everything is configured properly and you use pgsql > 10.7, the only idea I have is that Kaspersky (partly) blocks network traffic coming from an executable, which it doesn't know. But that's where my knowledge ends and you have to turn to the Kaspersky support.

Thank You so much bro <3 for great support
by the way i am using postgresql version 14 the latest one

i agree with you there's a problem on kaspersky they partly affect any unsigned software when connecting to postgresql ... (kaspersky set my tested softwares as (low restricted which is the best group when application doesn't have digital signature) in application control

Low Restricted. This group includes applications for which the following conditions are met: Applications are not digitally signed by trusted vendors. Applications are not recorded in the trusted applications database of Kaspersky Security Network.

@SGaist Thank you.

Hi and welcome to devnet,

That's a question you should rather bring to the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

@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.

Hi and welcome to devnet,

If you can reproduce this easily with a minimal compilable example, you should go to the bug report system to see if it's something known. If not please consider opening a new report providing that example and the guidelines to trigger the bug.