QML and Qt Quick

Was there ever a response to this issue? Any camera I query returns no supportedFeatures.

Camera enumeration and image capture works fine but regardless of camera no controls work, Exposure, WhiteBalance, Zoom, etc.

@GrecKo said in timing of sizing calculations:

The ListView has no width set in the code you pasted.

Right you are. I added explicit width to the ListView, and it now seems to size properly. I guess the console logs I put in were a bit misleading. Thanks!

@iliya-faramarzi
Apologies for the confusion about the styles—that was on me. Thanks so much for your help!

@hvoigt got the same issue

The issues are just a summary of the compile out put. It’s Tab Nr. 4 according to your screen shot.

If I force software rendering via QQuickWindow::setGraphicsApi, I don't see the ugly text. However, I do see it with both Vulkan and OpenGL rendering on Linux (on my Intel GPU). I did just make a breakthrough, though. If I set QT_FONT_DPI=120, as ChatGPT suggested, the issue goes away (on the QML Label, not on the Canvas). Maybe this is a known issue on Intel GPU? My Qt app detects logical DPI as 96 and physical DPI as 78.7852.

At least there's a bug filed for it: https://bugreports.qt.io/browse/QTBUG-122738

@GrecKo

Wow, this looks interesting. Thanks for sharing

Nevermind, I implemented my own QQuickItem which uses the QML scene graph, following this example:
https://doc.qt.io/qt-5/qtquick-scenegraph-customgeometry-example.html

Hi, On Qt 5.15.9 version，Ubuntu 22.04 , GNOME Desktop Manager.

SystemTrayIcon{ id: sysTray visible: systemTrayMode iconSource: "../image/logo.png" menu: Menu { MenuItem { text: qsTr("Show Application") onTriggered: { mainwindow.show() mainwindow.raise() mainwindow.requestActivate() } } MenuSeparator{ } MenuItem { text: qsTr("Quit") onTriggered: Qt.quit() } } onActivated: { if(Qt.platform.os !== "osx"){ mainwindow.show() mainwindow.raise() mainwindow.requestActivate() } } onMessageClicked: { mainwindow.show() mainwindow.raise() mainwindow.requestActivate() } Component.onCompleted: { } } Connections{ target: AppSettings function onHasSystemTrayIconChanged() { if (systemTrayMode) { sysTray.show() } else { sysTray.hide() } } }

After sysTray is displayed, no matter how the systemTrayMode changes, sysTray will not hide.

Yep. Create a .pro and open from QtC

Hi and welcome to devnet,

You shouldn't need to add the module to your include.
Are you sure your project is properly setup ?

@TomZ said in Exposing already defined enum to QML:

enums are always a mess, basically the general idea to have a clean namespace with enums doesn't work with QML.

It does work fine with namespaces. Q_ENUM needs to be made in the scope where the enum was defined though, it doesn't work with an already defined enum. And this requirement exists for both object/gadgets and namespaces.
The code you linked would have been fine with a namespace.

Also don't use qmlRegister*** in Qt 6, QML_*** are preferred.

Your connect is executed multiple time. Hence it is executed multiple time. If you do 10 time, it will execute 10 times as well :).

I'm not sure what is the semantics of the connect here ?
What is deviceList ? Where is the method qFanPropsUpdate(). Since you are disconnecting it perfectly ok.
Component.onCompleted: {
deviceList.forwardDevicePropertyChanged.connect(qtFanPropsUpdate)
}

@JonB It appears the problem was in my testing after updating the latest code here (Also it was always 10,000 data points, I wrongly wrote it as 1000.. I over-worked this issue. I will mak an edit. ). CPU usage has come down to 18% from 60%. I had done following things-

Moved LineSeries update to backend

LineSeres clear + append is replaced with replace

Qt is upgraded to 6.8.0

I am not sure which one out of this helped but results look better now. Thank you so much everyone who spent their efforts to read my long question and provide amazing ideas. Appreciate it.