Skip to content
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.

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

Open
flyleier opened this issue Nov 7, 2023 · 10 comments
Assignees

Comments

@flyleier
Copy link

flyleier commented Nov 7, 2023

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

@wangwenx190
Copy link
Owner

It should not be relevant to the commit you referred

@wangwenx190 wangwenx190 self-assigned this Nov 8, 2023
@flyleier
Copy link
Author

flyleier commented Nov 8, 2023

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.

@wangwenx190
Copy link
Owner

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

@wangwenx190
Copy link
Owner

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

@wangwenx190
Copy link
Owner

What's your Win10 version number?

@flyleier
Copy link
Author

flyleier commented Nov 9, 2023

What's your Win10 version number?

Windws10 Home 22H2 (19045.3570)

@flyleier
Copy link
Author

flyleier commented Nov 9, 2023

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.

@wangwenx190
Copy link
Owner

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

@wangwenx190
Copy link
Owner

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

@flyleier
Copy link
Author

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

Thanks, I have downgraded Qt version to 6.4.3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants