@chenPeng First, you need to click Download OpenSSL Button to install android_openssl.

@SGaist Thank you very much! It works perfectly now

Well, Qt does not provide these capabilities. This means that you cannot easily use stylesheets for this purpose. However, there might be OS-specific ways to change the color of the title bar. On Windows (10 and later) you can use DwmSetWindowAttribute to enable dark mode for the title bar. Another way is to get a window without decoration/borders from the OS and then draw the entire title bar yourself using Qt. Then, you can also style the title bar using stylesheets. It might get a little complicated to draw the close and minimize buttons in the correct OS style yourself.

@JonB thanks

@kkoehne said in QDoc doesn't generate all the documentation.:

MMh .. sounds indeed that something goes wrong here, then.

Can you create a somewhat minimal example, and open a bug report at https://bugreports.qt.io/projects/QTBUG, component 'Build tools: qdoc'?

Sure!
I'll prepare something. Maybe it's a particular configuration that leads to some kind of problem.

Thanks a lot in advance.

I'll keep you posted :-)!

I can't reproduce this on macOS 12.3.1 with Qt 6.3. Works as it should.

Copy qopensslbackend.dll in a tls folder next to your .exe, and DLL in your PATH :

./myexec.exe
./libcrypto-1_1-x64.dll
./libssl-1_1-x64.dll
./tls/qopensslbackend.dll

@jsulm said in How to get Qt5.15 on Windows ?:

@plaristote said in How to get Qt5.15 on Windows ?:

It seems that there are no available binary builds for Qt5.15... unfortunately

There are - why do you think there are not? Use the online installer - it provides Qt 5.15.x.

Agree with @jsulm. The installer is at https://www.qt.io/download-open-source

@JonB: yes, and then use QString::fromUtf8()

Here's my solution for this, in case anyone's interested:

The header file:

#include <windows.h> #include <dbt.h> #include <QObject> #include <QAbstractNativeEventFilter> class DeviceEventFilter: public QObject, public QAbstractNativeEventFilter { Q_OBJECT public: DeviceEventFilter(QObject *parent); bool nativeEventFilter(const QByteArray &eventType, void *message, long *result) Q_DECL_OVERRIDE; Q_SIGNALS: void notify(); };

And the source file:

#include "eventfilter.h" DeviceEventFilter::DeviceEventFilter(QObject *parent) { Q_UNUSED(parent) } bool DeviceEventFilter::nativeEventFilter(const QByteArray &eventType, void *message, long *result) { Q_UNUSED(eventType) // unneeded as long as we're only running on Windows Q_UNUSED(result) MSG *msg = (MSG *)(message); if ((msg->message == WM_DEVICECHANGE) && (msg->wParam == DBT_DEVNODES_CHANGED)) { emit notify(); } return false; }

Hola

Pues el error no dice mucho. Comprueba que tengas suficiente espacio en el disco para la instalación y que tengas permisos de escritura.

Si aun teniendo espacio te sigue dando el error, prueba a instalar como administrador, aunque yo nunca he necesitado hacerlo.

Un saludo

@aha_1980 Here's how I bootstrapped new working settings for QtCreator.
On Windows the settings reside in <user>\Appdata\Roaming\QtProject, which contains files QtCreator.db, QtCreator.ini and directory qtcreator with lots of subdirectories, xml files etc.
Renaming that directory then running QtCreator created a new settings directory (from a template kept in the Qt distro) . After that, QtCreator started behaving normally, though of course without any memory of previous projects or kit associations.
Copying the QtCreator.ini file from the renamed directory restored those memories but did not make the bad behavior come back.
Apparently the root problem is an incompatibility between Qt Creator 4.10.2 and some old file in the settings folder. In my case those files were created years ago by QtCreator 3.5. And since 3.5 does not even support VC 2015, I guess it was high time for a change.

@aha_1980
Hi again!
I created a bug report at https://bugreports.qt.io/browse/QTCREATORBUG-23295, lets hope that someone finds a fix. Thanks for your time!

@Yash001

That is beyond my experience level. No help possible from my side.

Ok i found the problem i just forgot to put the config file in my Deployment folder.
Thanks for the help @jsulm .

I ran into the same problem, where a closed QDialog would magically appear over a QMainWindow when hovering over the programs' TaskBar icon...
I understand that QDialogs do not get shown in the TaskBar thumbnail, but how does the Dialog appear out of thin air, after dismissing it??

@GreenSadFrog said in Incorrect QDialog view in Windows 10 taskbar:

If you click on the thumbnail (activate the window), QDialog will hide quickly to the correct state.

The problem OP described doesn't have anything to do with the Dialog not being shown in the Thumbnail btw

Seems to be a known bug https://bugreports.qt.io/browse/QTBUG-48855

@J.Hilk Thanks for your answer. But I want to ask how can I know I have to choose one over the another?

After running the application "Bluetooth File Transfer" I faced the following error:

0_1539775150775_Error.PNG

Thanks in advance!

Ok, I have not found a solution but a workaround.

I have to open and close the external window before my QML gui is opened.
So I do this in my main before the QML engine loads the QML file.
Then I pass the necessary information from the external window via pointers to my GUI.

I did some exploratory debugging and found that (on Windows 10) QWindowsStyle::drawPrimitive() is not being called to render checkboxes, but rather they are being drawn with DrawThemeBackgroundEx() from uxstyle.dll (which I would have expected to support High DPI correctly.)

After looking at the screen shots attached to the ticket referenced above I discovered that I have a different sort of drawing problem; checkboxes are being render correctly, but at the same size (13px) regardless of device scaling.

On Windows 7 checkboxes appear to render correctly with device scaling enabled.