wangwenx190 / framelesshelper

Project moved to: https://github.com/stdware/qwindowkit Cross-platform window customization framework for Qt Widgets and Qt Quick. Supports Windows, Linux and macOS.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Global::Option::ForceHideWindowFrameBorder causes the frame border to be weird on Windows

flyleier opened this issue · comments

FramelessConfig::instance()->set(Global::Option::EnableBlurBehindWindow);

In the mainwindow example, and in the main.cpp, change the code
FramelessConfig::instance()->set(Global::Option::EnableBlurBehindWindow);
to
FramelessConfig::instance()->set(Global::Option::ForceHideWindowFrameBorder);

the mainwindow has a weird border, in fact, shouldn't have a border.

I did some simple backtracking, I think that this bug was brought in in this commit : 415fb55

issue_fh

It should not be relevant to the commit you referred

It should not be relevant to the commit you referred

Sorry, I forgot to specify my environment: Windows10 + Qt6.5.3 + MSVC2019.
I rolled back repository to before the commit I referred and the bug is gone, however, as you said, it's not relevant.

So it seems it's caused by a commit after 415fb55, but I'm sure it's certainly not relevant to 415fb55. Let me investigate which commit is the bad commit

testing with Qt 6.5.2 and 6.6.0 on Win11 doesn't have this issue.

What's your Win10 version number?

What's your Win10 version number?

Windws10 Home 22H2 (19045.3570)

testing with Qt 6.5.2 and 6.6.0 on Win11 doesn't have this issue.

I did some testing on Win11 + Qt6.5.3, this bug is still appear, I think it is caused by Qt6.5.3. As a side note, if resize the window, the werid border will disappear.
In the commit 415fb55, I found some changes like this #if (defined(Q_OS_WINDOWS) && (QT_VERSION < QT_VERSION_CHECK(6, 5, 3))), it might have something to do with this issue.

I have no way to fix this issue perfectly. You need to either downgrade Qt version or build a new version from source yourself.

Currently Qt 6.5.3 & 6.6.0 are known to has this bug.

Currently Qt 6.5.3 & 6.6.0 are known to has this bug.

Thanks, I have downgraded Qt version to 6.4.3