The crash is caused by the line seriesList: myGraph.pieSeries in main.qml More precisely, the debugguer says me that the problem happens in the QGraphsView::insertSeries (internal method) because the QGraphsView object is nullptr. So far, here is my understanding. All the "Missing QML.Element" messages are displayed when I add the line import QtGraphs in main.qml. Because it seems that nothing is loaded correctly, the GraphsView is not created which finally provokes the crash. So I guess that if I fix the "Missing QML.Element" messages, everything will work fine.

@RokeJulianLockhart From what it looks like, QT is still being used on both Windows and macOS for the drop-down that shows recently synced files (and other parts of the app that look identical cross-platform). However, OneDrive's settings page appears to be using React Native on both platforms (Windows/macOS) to render native XAML/AppKit components on their respective platforms.

I see this is an old thread and I see several unresolved threads on this topic. I'm leaving this incase it helps someone else who ends up here. The solution was twofold for me. Go to File > Export Project and select Enable Python Generator. This will create a main.py. Make sure you pip install PySide6-DS Hope this helps someone.

Hello i am using WinCC OA to develop a qt application. WinCC OA has some custom elements which cannot be detected by squish for example a polygon. Squish is now not able to detect this element with the picker. I know the name of the element but as it is of WinCC OA internal i do not know the type: waitForObject( {"container": "container", "name": "POLYGON1","type": "???","visible": 1} ); How do i get this information? And what to use if unknown? Is there any other way? I mainly just need to click this element. Thanks a lot

Thank you 😊

Oh right, I forgot about that one. Depending on the content you can apply the same to rows. In any case, since your issue is fixed, please mark the thread as solved using the "Topic Tools" button so that other forum members may know a solution has been found :-)

@Max Ok, j'ai compris : en modifiant la taille de la fonte du QLineEdit inclus dans le QTimeEdit, ça fonctionne. Bêtement je prenais la police "f" du QLineEdit inclus, modifiais la taille de "f" et faisais QLineEdit->parent->setFont(f). Ici "parent" était de trop. En me relisant, j'espère que ce que j'ai écris est compréhensible... A+ Sylvain

@RokeJulianLockhart to the best of my knowledge, no. The first release of Discourse was in 2014 and the forum is several years older than that.