General and Desktop

@QuocKhanh Yes, QObject::connect() can make cross-thread connections. Why you would want to do this with QSerialPort, or what you have done that "didn't work", would have to be explained by you.

@Perdrix It has dead simple integration with Visual Studio and when you later might want to use CMake for building it is also easy to use. libraw, libtiff and boost are available and it would simplify things quite a lot for newcomers.

Solution found. Issue closed. In *.pro file: DEFINES += SOME_VALUE Here full explanation https://stackoverflow.com/questions/3348711/add-a-define-to-qmake-with-a-value

@Xav12358 Then I'm afraid I don't know since it's some PyCharm debugger issue.

@Paul-Colby Thanx.

@mjsmithers said in const function causes garbage collection crashes with QMap.: experiment more with Qmap::value(), although it's not clear from the documentation if it returns a copy or a const reference. As per my previous, I think this is 100% clear?

@ChrisW67 said in How to execute command installed with snap: Then the relevant directory is not in the PATH inherited by your process. On my Ubuntu machine the /snap/bin directory is in the system-wide path. Which is as I wrote above. However, I do not see a connection between lpr and snap. On a generic Ubuntu machine lpr is a compatibility tool installed as a native application by CUPS: I agree, this has nothing to do with snap. It should be in /usr/bin. That should be on $PATH already. @Stormbringer1900 said in How to execute command installed with snap: If I try QProcess::execute("whereis lpr"); there's no reply. whereis itself is in /usr/bin/. If by any chance, somehow, /usr/bin is not on PATH then the whereis itself will fail to execute. What is the return result from QProcess::execute()? Did it write anything to stdout/err? Probably the first thing to try is echo $PATH # or possibly /bin/echo $PATH Compare calling via QProcess from Qt app against what it is in external shell where lpr etc. work.

@SimonSchroeder said in QThread infinite loop: //-----8<--------------------------------------------- QThread *thread = new QThread(); thread->start(); // could also be done later MyClass *obj = new MyClass(); obj->moveToThread(thread); QTimer *timer = new QTimer(); timer->setInterval(1000); QObject::connect(timer, &QTimer::timout, obj, &MyClass::periodicFunction); timer->moveToThread(thread); timer->start(); Multithreading is hard! The timer->start() should come before timer->moveToThread(). I would also establish the connection from the QTimer instance to MyClass instance before moving the later. It's paranoia in this case, but prevents connecting to deleted objects in some realistic scenarios.

@Ggwp1234 I think you should show a window in the first place, or maybe you mean to use applicationStateChanged signal ?

@AndrzejB the installer does nothing in that regard. They are generated if memory serves well.

@cdvo I found my way. I removed all designer*.qm files under the translation folder but left the en one. Thanks

As long as you don't access the object via a non-const function there is only one QString instance with '"some Text"'.

@jsulm No it does not build.

@Oeschi said in How to fix application crash under Win11: ExceptionCode: 0xe0464645 Searching for this seems to generate hits all to do with NVidia gfx card? In dwm.exe.

@Amos-graham No need to change anything in your account. Simply select the OSS version when installing Qt.

@samfallday said in QtSerialPort and FTDI Driver Issues: I assume these other 3rd party programs are built on the Windows API and that is what makes the difference. Qt is using the same windows api as other tools - they don't add some magic new functions to Qt. You have to find out what they're doing different to Qt.