General and Desktop

@JonB You're right. I always launch one wsl process in one cmd window, and wsl processes in different cmd windows can live with each other. Now I tried launching multiple wsl processes in one cmd using start /b, the result is the same as this demo application: all wsl processes will exit immediately. So the problem is multiple wsl processes cannot be launched by a single parent. It has nothing to do with QProcess.

Include QStringList header

@JKSH Sorry, i have another question. In this video https://www.youtube.com/watch?v=bwTlCBbB3RY at the 18:20 he talking about "Displaying License and Copyright in GUI": It looks like for each module I need to specify the copyright (and not just the Qt copyright, but all the copyrights from all the source files in the module), the GPL/LGPL license text, modifications (if any), the used-license (what is that? Should we just show the LGPLv3 text when clicking on this menu or something else?). So I need to duplicate this information for each Qt module I will use and it is not enough to provide the common text for all modules once?

@thomasGl You can do that with https://doc.qt.io/qtdesignstudio/

Hi and welcome to devnet, For testing frameworks, Qt already provides the QTest module which works pretty nicely. As for the rules, there's mainly one: test both happy and unhappy code paths. That way you ensure that your code is working when everything goes well as well as when issue arise.

Hi, I don't think you missed anything. One possible I can imagine is to create a wrapper function that you would use in your route that would measure the execution time of the real function that you would have passed to said method.

@Pl45m4 honestly, I haven't decided how best to implement it, I thought maybe there was another alternative? I didn't fully understand what you meant, just store in the auxiliary structure not the data but the list of connections?

Seeing this behavior on Windows with 6.8.3, was there a QTBUG tracking this behavior and/or fix that may have more information?

@Christian-Ehrlicher Thank you. I found that after I add -DCMAKE_BUILD_TYPE=Debug when I build qoci the qsqlocid.dll, etc. are built and installed, then the problem can be fixed

@Christian-Ehrlicher I'm using gcc 8.5.0 I honestly can't tell where in the code the error is occuring because the output is so long. I've been building this applciation for years using various versions of Qt, but I haven't seen these errors before. It builds without error under Qt 6.6.3. I can try a simple program to see if I also get the errors there.

Currently, my dialog is something like this (see attached image) i..e no title bar. I want it to be a modal which blocks interaction with it's parent and at the same show title bar. Above solution doesn't works for mac. However below code works fine on ubuntu 22.04. I think this is platform specific issue. class MyDialog(QtWidgets.QDialog): def __init__(self, parent=None): super().__init__(parent=parent) self.setWindowTitle("My Dialog") # Set modality to WindowModal self.setWindowModality(Qt.WindowModal) # Set appropriate window flags # self.setWindowFlags(Qt.Dialog | Qt.Window) # Set up the layout layout = QtWidgets.QVBoxLayout(self) layout.addWidget(QtWidgets.QLabel("This is a dialog!")) self.setLayout(layout) class MainWindow(QtWidgets.QMainWindow): def __init__(self): super().__init__() self.setWindowTitle("Main Window") self.setGeometry(100, 100, 300, 200) # Add a button to the main window self.button = QtWidgets.QPushButton("Show Dialog", self) self.button.setGeometry(100, 80, 100, 40) self.button.clicked.connect(self.show_dialog) def show_dialog(self): dialog = MyDialog(self) # Create dialog with main window as parent dialog.show() # Show the dialog (exec creates a modal dialog) [image: 2b98569d-09be-42a2-8c14-987c693745f7.png] This is how it looks on Ubuntu---- [image: c6c43930-8717-429d-af63-363e1ffd849c.png]

@mirro As @SGaist says. stackoverflow is really the reference for questions about programming, be that C++ or PowerShell, e.g. start from https://stackoverflow.com/questions/tagged/powershell. You will have to be quite "formal" in a posted question, e.g. your code would need posting as text not as a screenshot.

Looks like a debug build to me, maybe mixing release and debug is not a good idea on a Raspberry Pi. Also, it is a Raspberry 5 not a 4, right?

@Christian-Ehrlicher Hi, I found that if I downgrade CMake to 3.28 and change line 20 back to FetchContent_Populate then the CMake build can run successfully. I learned that different from FetchContent_Populate, FetchContent_MakeAvailable not only downloads and unpacks the content but also automatically adds it to my build by calling add_subdirectory() internally. Aftter I remove add_subdirectory(${ds_SOURCE_DIR} ${ds_BINARY_DIR}) then the CMake build can run successfully

I tested it with a recent Qt6 version and could not see any pushbutton at all.

I tried all the ViewportUpdating Modes of QGraphicsView but it didn't work. However, when I didn't set QOpenGlWidget to the viewPort of QGraphicsView, triggering an update for a single item in the same scence wouldn't trigger the paint function for other items

I updated to Qt 6.9.0 and Qt Creator 16.0.1 and problem disappeared!

Hello Dale, would it be possible for you to share what you did to make it work? Even though you call it a hack it would be interesting to see how it is possible to prevent the code from hanging during shutdown.