General and Desktop

@bxrs Please use the forum's Code tags (</> toolbar button) when pasting blocks of code. I presume that clientSet.cpp has #include "ui_clientSet.h" to include the .h file generated from the .ui file by running uic. And that file lives in the build output directory, not the source directory, and is being regenerated correctly? Start by replacing MainWindow w; by QMainWindow w; and report back as to whether that shows correctly. Then take it from there. Reading again, I am unsure whether "Why does the client set interface not display after the program runs" means you do not see any window/widget open and appear on your desktop (per my answer above) or whether you mean you do see a main window but it is empty/does not show what you designed into the .ui file? If it's the latter, check what is in the .ui file and in the generated ui_clientSet.h file. An occasional mistake is to find a file of that name somehow lying around in your sources directory, it must not be there. The one regenerated each time from changes in the .ui must be located in the build output directory and must not be overridden by one sitting in the source directory, check for that?

Thanks a lot! with your help, the split worked.

Doing such stuff in showEvent() is not a good idea - it is e.g. also called when the window is minimized and restored. Why it happens in your case - I don't know. Maybe you can find out by looking at the backtrace during debugging. Maybe set a flag in doStuff to do it only once.

Thank you very much. This also set me on the direction to explore stylesheets with a better understanding.

I don't use QWidget::grabMouse()

@Christian-Ehrlicher Oh well, did not expect the solution to be that simple (if this is actually the case) Understanding the Qt Framework's library/module design is pain :D

See 'qtvars.log' in 'qt/qmake' in project build directory (may differ from solution build directory). For example, '<ProjectDir>/x64/Debug/qt/qmake'. In this 'qtvars.log' may contain a real error description.

QT has a thread that processes the events, and this error indicates that your program is forcing QT to reparse the events. Why does your class extend public QObject? And you decorated the class with Q_OBJECT. If I were you, I would remove the public QObject and re-test

@Bonnie I fixed buffer in JS and solutions are the same. JS result: <Buffer 01 00 00 00 00 07 54 e4 86 bf 6c 74 16 1e 64 c8> <Buffer 67 45 23 01 67 45 23 01 0c 2f 91 01 00 00 00 00> <Buffer f3 69 3e d6 74 eb 39 33 03 9a 61 fd f7 a3 50 03> Qt result: eCommandLine: "01000000000754e486bf6c74161e64c8" Size in bytes: 16 EncryptKey: "67452301674523010c2f910100000000" Size in bytes: 16 DATAcrypt: "f3693ed674eb3933039a61fdf7a35003" Size in bytes: 16

@JackJ30 said in How to place widget on top of embedded QWindows: QtWidget:: createWindowContainer returns a QWidget*, so you can put other widgets on top of it like with any other widgets (set the widget returned by createWindowContainer as parent).

For anyone who cares in the future, the closeEvent on the mainwindow works. It's jank, but it works.

@jsulm said in Can't update Qt: Try another mirror. See "Selecting a mirror for opensource" in https://wiki.qt.io/Online_Installer_4.x That should also work with the Qt Maintenance Tool. I try use mirror like ./maintenancetool.exe --mirror http://qt.mirror.constant.com and start loke admin, and it's work. Thanks!

Thanks for all your answers: the problem was that the old code was pulling QtPrivate::QDebug the semaphore was from the QDebug initializing (I imagine to serialize the output) and the memory allocation was the same issue QDebug tried to allocate an output buffer with a long initialized variable I removed the code, and now everything works.

@GrecKo You are right, the problem lies elsewhere, In an effort to post the minimal code I removed the problem from my code. It does not seem related to timer anymore but to other functions I call. Now I can find where the problem really comes from. Thanks :)

I interpreted the error as indicating that the labssettings DLL was not found. After renaming the DLL, I received a different error stating that the DLL was not installed. That made me realize that the first error actually meant there was a missing dependency in labssettings. I identified and copied the missing DLL, which resolved the issue. In the end, everything is easy.

Sorry, I currently don't have a Windows machine at hand. One additional thing you could do is create a minimal compilable example. That way, fellow forum members will be able to try and reproduce your issue on the same conditions you have.

@Dyenhen To be clear, you have to add the options yourself to the menu. There is no preset configuration which says "Save as SVG", in case you were looking for something like that...

I've amended the title of the post because the problem seems to be just with Mint 22.1. It is still strange why it won't work though, given that it has worked on all Mint systems for the past 7 years or so. I'm still hoping someone has an idea because rebooting just to work on a project is very inconvenient, to say the least!