@J-Hilk
Thanks. It solved my doubt.

@newbiSoso I think you have to play with the background property, something like this:

Popup { id: popup anchors.centerIn: parent background: Rectangle { anchors.fill: popup border.color: "black" color: "transparent" } Text{ text: "Game Over!!" + "\n\n" + "New High Score: "+ score_val anchors.centerIn: canvas color: "grey" font.pixelSize: 70 font.family: gill.name } modal: true focus: true closePolicy: Popup.CloseOnEscape | Popup.CloseOnPressOutsideParent }

@LeLev Thank you very much for the code sample!

@QTLeearn said in How to implement this shape?:

can we use sth easier like: ShapePath type?

yes, you can try

main.qml looks like this:

Window { //... Item { id: listViewContainer //... ListView { id: listview //... model: ListModel { ListElement {component: "Datasheet.qml"; } // TableView ListElement {component: "PieChart.qml"} ListElement {component: "BarSeries.qml"} } delegate: Loader { //... }

I know how to make use of the TransactionsModel in Datasheet.qml

model: TransactionsModel{ id: transactionsModel; modelTransactions: transactions }

How can I define this model once in the main.qml and distribute it to Datasheet.qml, PieChart.qml, BarSeries.qml?
Or is it not how it should be done?
Should I have three models, each for Datasheet.qml, PieChart.qml, BarSeries.qml?

That's a good resource. You'll need shaders to achieve that effect.

@vamsi1992 Great, don't forget to set the topic to solved, if your issue is solved :)

You can install your own message handler and disable logging there shortly before the transition starts. Docs. But, it's very probable that logs are not the cause of issues here. Try disabling them completely for the whole app and see if that changes anything. Then use a profiler to identify the bottlenecks.

@GrecKo said in QList<QObject*> as member that can be used as a list:

How is that better than a QObjectList?

i don't know, tell me

@IntruderExcluder Thanks!

@Pradeep-P-N Thank you very much :)

@neda said in How can I fix bug camera in Qt5.13.1?:

I wanna adjust exposure related settings in my camera. For example I try to use function "camera.searchAndLock()" but it doesn't work.

What hardware are you using (i.e. webcam attached to USB, Android phone camera, Raspberry Pi camera, etc.)?

Are you positive that the underlying hardware allows for all those settings (i.e. focus lock, exposure, manual shutter, etc.)?

Have you tried that same hardware with a different (non-Qt) application?

I have the same problem, Qt 5.12.6 mingw73_64 Creator 4.7.1 on Windows 7 Pro 64-bit. It only happens in release mode, even though there is no mode-dependent setting in my .pro file. I do not use QSettings explicitly, but when I fail to set the app's organisation/domain name I get a complaint from QSettings, so it does seem to be invoked behind the scenes.

I'm actually chasing the problem that the packaged (with windeployqt) application exits cleanly without doing anything whatsoever, while it works just fine (in debug and release mode) in Creator. Landed here because this error message is my only clue at this point...

@Anita The difference is that if shadow build is activated you will get a build directory outside of your project source directory where all build artefacts will be (such as your executable). This has several advantages:

Your source tree is not polluted with build artefacts (especially useful when using CVS) You can build for different targets with different configurations without destroying your other builds (each configuration will have its own build directory) You can easily do a complete clean rebuild: simply delete build directory and build

Tests work with shadow build also.

@Shrinidhi-Upadhyaya This code?:

Repeater { id: repeaterID model: [7,8,9,4,5,6,1,2,3] delegate: PushButton { id: theButton height: 75 width: height text: modelData onClicked: { console.info(entryDisplay.selectedText.length) if(entryDisplay.selectedText.length > 0) { console.info("first") console.info(entryDisplay.selectedText.length) entryDisplay.text = modelData } else { console.info("second") console.info(entryDisplay.selectedText.length) entryDisplay.text += modelData } theButton.forceActiveFocus() } } }

I really can't understand why it's not working for me. I wish I was better with the QML debugger. Perhaps I will try re-writing the whole component. There must be a deeper problem.

@IntruderExcluder

Thanks! that works.