To close this topic: I went for a launcher approach: Three binaries, one raw console app, one GUI app and one GUI launcher which allows you to start the program by running one of the other two executables. Selection either in its own GUI or silent by using args for the launcher itself, i.e. myAppLauncher -gui myAppLauncher -cli

@JonB Yeah, I could do something similar, iterate over all widgets and pass on the event. Thanks, I will try this method in the final application.

@Jammin44fm Normally you use process events when you have differents events that can impact or slow down the main thread . In the main file you just want to start your application.Is there even in your main file that can impact the main thread?following your code no.So you can't call QApplication::processEvents() in the main.cpp Now a situation where you can use QApplication::processEvents() for instance, lets say you have an application that capture frames from the camera , display that in the UI and also send them to a server. This in a situation where we have multiple events.Now when handling these events you can use in one of them QApplication::processEvents(), or QThread to avoid that the app freezes

@Jammin44fm Thanks for everyones input I've traced the issue to a problem with process input, and i'm going to create a more specific issue to address that.

Announcing that this problem is solved. I am really appreciate and grateful to your suggestions and advice, after all the segment fault is no more occur. 🙏🏻. It troubles me for around a week.

@jsulm Thanks , yes I missed this. now It's working ! Thank you

@SGaist said in Re-activate (known as create a new substance) a QMainWindow after the last QMainWindow is closed: Based on this feature request, you should be able to react on the ˋQEvent::ApplicationActivate`. I'm using that in a subclass of QApplication. The idea in pseudo code: void Application::applicationStateChanged ( Qt::ApplicationState state) { if(state==Qt::ApplicationActive AND no window is open AND OpenUntitledWindow ) { openNewWindow(); } OpenUntitledWindow is a flag setting if an new window/document should be opened on startup, it works also when the app is reactivated with the code above.

@gouneken multiple inheritance of QObject isn't possible (Page_all class) your Page_all class inherits QWebEnginePage and also has a QWebEnginePage as a member variable?! dont name variables the same as their type names! the createWindow() method is intended to create a new physical window (a QWidget for example) and return the containing QWebEnginePage. You might need to create another QWebEngineView inside (or a use it directly as a window)

When I researched having both a GUI and command line application on Windows I stumbled upon how Microsoft does it itself with devenv. They provide a .exe and a .com at the same time. If you call your software myapp then you should compile the GUI application to myapp.exe and the command line application to myapp.com. When typing myapp on the command line it will launch the .com version. What we did in addition is to have the two application call each other depending on the command line parameters. This is a better user experience than attaching a console. With qmake use an additional CONFIG to select between GUI and console (e.g. CONFIG+=console when calling qmake). In your main() have #ifdefs to switch between command line and GUI during compilation.

@geodoomgr: your tip helped, now works great on QT 6.6.3 thanks

@J-Hilk Thank you for answering the question.

Sorry but I still don't see why you need to delete and re-create the proxy style. But do what you like.

See https://bugreports.qt.io/browse/QTCREATORBUG-26918

Thank you @hskoglund for this option, it worked! This is the perfect solution for me, it's simple, and now I can use C++ variables for the install path of my DLL if needed. Thanks again!

PATH ? Why did you change that environment variable manually ?

Hi. I think it just for a static QObject like QFile in Application ... It can solve with static function to create a static object in first call...

@Dariusz If you check the PySide documentation you will see that there is no overload taking a lambda or any function/method. There are only overloads accepting strings containing method name. So, it seems not possible with PySide. But instead of using QApplication instance you could create your own class with methods you want to call using invokeMethod.

Hi As far as I know, there is nothing like that in Qt. It can blur widgets but not the actual desktop.