From 9cb93364d920c848908ead35e0e12ae478d17563 Mon Sep 17 00:00:00 2001
From: Sine Striker <trueful@163.com>
Date: 周二, 10 9月 2024 14:15:29 +0800
Subject: [PATCH] Update version

---
 README.md |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index cfd881a..91db452 100644
--- a/README.md
+++ b/README.md
@@ -7,9 +7,12 @@
 
 Feature requests are welcome.
 
-## Join with Us :triangular_flag_on_post:
+## Stay In Touch :triangular_flag_on_post:
 
-You can join our [Discord channel](https://discord.gg/grrM4Tmesy). You can share your findings, thoughts and ideas on improving / implementing FramelessHelper functionalities on more platforms and apps!
+You can share your findings, thoughts and ideas on improving / implementing QWindowKit functionalities on more platforms and apps!
+
+- Chat with us on [Discord](https://discord.gg/grrM4Tmesy)
+- 涓枃鐢ㄦ埛鍙姞鍏� QQ 缇� 876419693
 
 ## Supported Platforms
 
@@ -273,17 +276,14 @@
 - Once you have made the window frameless, it will not be able to switch back to the system frame again unless you destroy your window and recreate it with different settings.
 
 #### Native Child Widget
-- There **must not** be any internal child widget with `Qt::WA_NativeWindow` property enabled, otherwise the native features and display may be abnormal. Therefore, do not set any widget that has called `QWidget::winId()` or `QWidget::setAttribute(Qt::WA_NativeWindow)` as a descendant of a frameless window.
-    - If you really need to move widgets between different windows, make sure that the widget is not a top-level window and wrap it with a frameless container window.
+- If you are about to add a widget with `Qt::WA_NativeWindow` property enabled as a descendent of the frameless window, you should enable `Qt::WA_DontCreateNativeAncestors` of it in advance.
 
 #### Size Constrains
 - If you want to disable window resizing, you can set a fixed size, which is officially supported by QWindowKit. If you use other special means to achieve this, QWK doesn't guarantee everything can still be fully functional.
 - If you set a maximized width or height, the window should not be maximized because you cannot get the correct window size through Qt APIs. You may workaround this by using system APIs such as `GetWindowRect` or `GetClientRect`. The root cause lies deep in Qt QPA implementations and currently we don't know how to fix it without modifying Qt itself.
 
 #### Windows 10
-
 - Due to the inherent defects in the Windows 10 window system, the top border will disappear when the system title bar is removed. We have filtered Qt's event and perfectly reshown the system top border, thanks to the implementation of Windows Terminal for our reference. However, this workaround only works with QtWidgets and QtQuick (**only when rendering through D3D**) applications.
-
 - In QtQuick applications that use OpenGL or other rendering backends, we use Qt's painting system to emulate this border. But since Windows 10 system border is translucent, the difference from the system border is more noticeable in a dark background.
 
 ## TODO

--
Gitblit v1.9.1