One of the things which I did in the past was, to write a C++, Qt5 application, which was meant as a test, of how to incorporate certain GUI elements into a program, those elements extending as far as, how to force the program to display with my own desktop theme, even on target computers that do not have this theme set or installed.
I was so focused on that aspect of the project, that I had overlooked a simpler aspect of it: What would happen if the user decided to resize the window. The initial window size is 850×720, and resizing, so far, was ugly. But, according to tonight’s update, the resizing behaviour has been made much nicer. (:1)
The relevant files can be found in the following directory on my site:
The files are the ones that begin with ‘
There is also a compiled AppImage that will run on Linuxes with at least ‘CXXABI_1.3.9′ (equivalent to Debian 9 / Stretch), but no binary to run under Windows. Sorry for that last omission. However, readers who have the Qt SDK installed, should be able to compile under Windows as well. What needs to be done, when Qt projects are being recompiled with another computer’s SDK, is, that the file ‘
Creator_Test6.pro.user‘, typically, needs to be deleted, as it contains details specific to one version of the SDK. Because of this, the Project Configuration – i.e., the Toolkits that are to become compile targets – will then also need to be redefined by any interested power-user.
There’s a small observation to add about this software project. The concept that it should display in its own desktop theme, only works fully, when running the AppImage under Linux. That is because I linked the Theme Engines and Styles in, using the command-line tool ‘
linuxdeployqt‘. Those were binary plug-ins, that I do not even possess the source-code for. Hence, if the reader custom-compiles the same project, they will find that those plug-ins have not been compiled, and that for this reason, the app will display with the local Style at best.
In reality, there are two separate settings:
Out of those, the first should even work if the reader custom-compiles, but the second should not.
(Updated 8/02/2021, 7h45… )