General and Desktop

@Axel-Spoerl, I only wanted to discuss it with them, but you've all answered everything I wanted to know. (I don't mean I was speaking on their behalf.) Thanks, all!

Just see here and here.

@Perdrix said in Size of QtWebEngine: Unfortunately litehtml won't work for me - I need function it doesn't provide :( That's pretty much the tradeoff. Chromium has All The Things you might need, but that means it has the disk usage of All The Things.

@JonB said in Physics Simulation Concept: Visualizing Mass-Varying Motion with Qt and Python: @zvoopz said in Physics Simulation Concept: Visualizing Mass-Varying Motion with Qt and Python: For raw range vs deflection of thrust estimation my cpu needs 30+ seconds I know nothing about all this physics, but if the rocket has to stop and spend 30 seconds calculating something that worries me... ;-) You are right. But this is a pre-launch estimation that determines a hundred of launch trajectories to select the closest pitch angle further. The longest trajectories have a real flight time about 400 seconds with calculations time step 1/1000 of second. Flight-time correction calculations won't last long. Plus qDebug console output logs eat a lot of time

@Perdrix said in QProcess::terminate() or QProcess::close(): All well and good but that presumes that the process in question accepts input asking it nicely to close (probably on re-directed stdin). In this case the help display process doesn't support that. I've now changed to use start() instead of startDetached() Actually that's not entirely true. For a normal command line program it would terminate on its own, such as "ls, ps ax, df,...whatever", but in your case it's a little different. The POSIX way to tell a child to die gracefully is to send it a kill signal, which is different from using close/terminate. kill(pid, SIGTERM) kills a process, and can be trapped by the child to do cleanup. But in all fairness the QProcess::close() probably does that implicitly, whereas QProcess::terminate() is not "nice" about it.

@bogong said in Add resource file (*.qrc) to static library. How?: How to add *.qrc files to library and how to use it in the main project? You would use qt_add_resources() for *.qrc files: https://doc.qt.io/qt-6/qt-add-resources.html However, if your *.qml files are inside a *.qrc then you won't get the full benefits of qt_add_qml_module() (such as optimization via the Qt Quick Compiler: https://www.qt.io/blog/the-numbers-performance-benefits-of-the-new-qt-quick-compiler). It is better to move all your files out of the *.qrc, and directly into the qt_add_qml_module(): qt_add_qml_module(${A_NAME_TARGET} URI Library_v1 QML_FILES ATestQML.qml BTestQML.qml RESOURCES myimage.png myotherimage.png )

@EduardoQtDev said in CMake problem with Qt 6.10.0: Just in case someone wants to open a bug report. https://bugreports.qt.io/browse/QTBUG-137577 - Known, and already fixed it seems. You'll need to wait for beta2, or build from Git.

One other possible option that might also make your users happy: have a setting in your application that allows to set the path to ffmpeg so if they have a custom version they want to use, they can change for it. You can populate that value checking for known paths.

in fact you need two structures : one core structure containing all the data, called the model, and a UI component displaying the data from the model. It is bit more complex and time consuming to setup than an excel/libreoffice spreadsheet, but much more lightweight and offers you more control and more protection on how data are displayed or edited, which cells are editable. creating a view in TableView { id: tableView anchors.fill: parent // or whatever anchoring/positionning/layout you want model: yourTableModel // should be declared nearby } Please note that TableView on it's own doesn't provide horizontal and vertical headers, you have to add VerticalHeaderView and HorizontalHeaderView manually. https://doc.qt.io/qt-6/qml-qtquick-controls-verticalheaderview.html for the model, you have two options : either you subclass QAbstractTableModel, adding a QML_ELEMENT macro after Q_OBJECT, and declaring those source files in a qt_add_qml_module directive in CMakeLists.txt The TableView documentation provides a minimal example of a model that can be used in a QML view : https://doc.qt.io/qt-6/qml-qtquick-tableview.html or you can use the ListModel QML element if your model isn't much complex. Option one is usually advised for production. Option two is often used by UI dev to supply a sample model to work on the view itself.

https://download.qt.io/official_releases/qt/

Hi, In addition to the questions of my fellows, one thing to consider for the tests is to write the file to a known read/write path rather than relying on system defaults.

The fact that Qt does not implement a direct method to generate QIODevice-like signals for stdin implies that doing so is difficult or impossible. The problem with using a separate QThread in the child to generate signals by blocking on sys.stdin.readline() is getting that QThread to exit. QThread.terminate() does not terminate that QThread until a line of input is received. All related answers ignore this problem. I was able to workaround this by having the parent process feeding the child's stdin send "exit\n", and have the child's stdin-reading QThread detect that line and call its QThread.exit().

@SGaist Thank you! This seems to work (well at least it compiles)! auto deepSkyStacker = DeepSkyStacker::instance(); connect(ui->help, &QLabel::linkActivated, deepSkyStacker, [=]() { deepSkyStacker->help(); }); David

I'm resurrecting this because I am facing the same issue. We are looking at Qt as a migration option from MFC (one of several). So I have VS Tools added to Visual Studio 2022. I have manually added the Qt "bits" to the relevant project file but I can't find a way of successfully adding this in to the Qt settings part for the project: CONFIG -= entrypoint I tried passing it on to qmake in the "Additional Command Arguments" but to no avail. There appears to be lots of things I could do with the "Qt Project Settings" within Visual Studio but if there's any documentation on this, I can't find it. TIA

@Christian-Ehrlicher said in Undefined symbol when trying to load a Wayland custom shell extension client plugin: Simply leave it empty so CMake will auto-determine the needed compilers. Yeah, if it's omitted it will default to C and CXX. The custom shell example has LANGUAGES CXX but that still works for the example.

@Kent-Dorfman, yeah, it would be if these were part of a program. However, these are my own files manually-created files in my own data drive. Being able to manage them in a Qt-based file manager (like KDE's Dolphin) would be useful. A human can't feasibly interface with a database for every file transfer, and I don't want to fork Dolphin to add something so niche to it just for me, since that really wouldn't help anyone else.

You should check the bug report system to see if it's something known and if not, please open a ticket providing minimal compilable example that triggers the crash.