| | |
| | | # QWindowKit |
| | | |
| | | Cross-platform window customization framework for Qt Widgets and Qt Quick. Support Windows, macOS, Linux. |
| | | Cross-platform window customization framework for Qt Widgets and Qt Quick. |
| | | |
| | | This project inherited most of [wangwenx190 FramelessHelper](https://github.com/wangwenx190/framelesshelper) |
| | | implementation, with a complete refactoring and upgrading of the architecture. |
| | | |
| | | Support as many system native features as possible without requiring additional dependencies. |
| | | |
| | | <!-- ## Why using QWindowKit? |
| | | |
| | | Here're why `QWindowKit` is better than `FramelessHelper`: |
| | | |
| | | + Full support of Windows 11 Snap Layout |
| | | + Most of the redundant codes and architectural flaws are eliminated, and the binary size compiled by MSVC is about 1/9 of `FramelessHelper` |
| | | + A critical issue that moving window forces the entire window to be repainted on Windows is fixed |
| | | + Capable to cope with WinId mutation, and `QWebEngineView` is perfectly supported |
| | | + Simpler APIs, more detailed documentation and comments |
| | | + A lot of bugs are fixed |
| | | |
| | | Feature requests are welcome. --> |
| | | |
| | | ## Supported Platforms |
| | | |
| | |
| | | |
| | | | Component | Requirement | Details | |
| | | |:---------:|:-----------:|:-------------------------:| |
| | | | Qt | \>=5.15 | Core, Gui, Widgets, Quick | |
| | | | Qt | \>=5.12 | Core, Gui, Widgets, Quick | |
| | | | Compiler | \>=C++17 | MSVC 2019, GCC, Clang | |
| | | | CMake | \>=3.17 | >=3.20 is recommended | |
| | | |
| | |
| | | |
| | | ## Dependencies |
| | | |
| | | + Qt 5.15 or higher |
| | | + Qt 5.12 or higher |
| | | + [qmsetup](https://github.com/stdware/qmsetup) |
| | | |
| | | ## Integrate |
| | |
| | | |
| | | ### Qt Widgets Application |
| | | |
| | | #### Setup Window Agent |
| | | |
| | | First, setup `WidgetWindowAgent` for your top `QWidget` instance. (Each window needs its own agent.) |
| | | |
| | | ```c++ |
| | |
| | | |
| | | MyWidget::MyWidget(QWidget *parent) { |
| | | // ... |
| | | auto agent = new QWK::WidgetWindowAgent(w); |
| | | agent->setup(w); |
| | | auto agent = new QWK::WidgetWindowAgent(this); |
| | | agent->setup(this); |
| | | // ... |
| | | } |
| | | ``` |
| | | |
| | | You can also initialize the agent after the window constructs. |
| | | If you don't want to derive a new widget class or change the constructor, you can initialize the agent after the window constructs. |
| | | |
| | | ```c++ |
| | | auto w = new MyWidget(); |
| | | auto agent = new QWK::WidgetWindowAgent(w); |
| | | agent->setup(w); |
| | | ``` |
| | | |
| | | #### Construct Title bar |
| | | |
| | | Then, construct your title bar widget, without which the window lacks the basic interaction feature, and it's better to put it into the window's layout. |
| | | |
| | |
| | | Let `WidgetWindowAgent` know which widget the title bar is. |
| | | |
| | | ```c++ |
| | | agent->setTitleBarWidget(myTitleBar); |
| | | agent->setTitleBar(myTitleBar); |
| | | ``` |
| | | |
| | | Set system button hints to let `WidgetWindowAgent` know the role of the child widgets, which is important for the Snap Layout to work. |
| | | Next, set system button hints to let `WidgetWindowAgent` know the role of the child widgets, which is important for the Snap Layout to work. |
| | | |
| | | ```c++ |
| | | agent->setSystemButton(QWK::WindowAgentBase::WindowIcon, myTitleBar->iconButton()); |
| | |
| | | agent->setSystemButton(QWK::WindowAgentBase::Maximize, myTitleBar->maxButton()); |
| | | agent->setSystemButton(QWK::WindowAgentBase::Close, myTitleBar->closeButton()); |
| | | ``` |
| | | Doing this does not mean that these buttons' click events are automatically associated with window actions, you still need to manually connect the signals and slots to emulate the native window behaviors. |
| | | |
| | | Set hit-test visible hint to let `WidgetWindowAgent` know the widgets that desire to receive mouse events. |
| | | On macOS, this step can be skipped because it is better to use the buttons provided by the system. |
| | | |
| | | Last but not least, set hit-test visible hint to let `WidgetWindowAgent` know other widgets that desire to receive mouse events. |
| | | |
| | | ```c++ |
| | | agent->setHitTestVisible(myTitleBar->menuBar(), true); |
| | |
| | | |
| | | The rest region within the title bar will be regarded as the draggable area for the user to move the window. |
| | | |
| | | Check [`MainWindow`](examples/mainwindow/mainwindow.cpp#L108) example to get detailed information. |
| | | |
| | | #### Window Attributes (Experimental) |
| | | |
| | | On Windows 11, you can use this API to enable system effects. |
| | | |
| | | ```c++ |
| | | agent->setWindowAttribute("mica", true); |
| | | ``` |
| | | |
| | | Available keys: `mica`, `mica-alt`, `acrylic`, `dark-mode`. |
| | | |
| | | ### Qt Quick Application |
| | | |
| | | Make sure you have registered QWK into QtQuick: |
| | | #### Initialization |
| | | |
| | | Make sure you have registered `QWindowKit` into QtQuick: |
| | | |
| | | ```cpp |
| | | #include <QWKQuick/qwkquickglobal.h> |
| | |
| | | // ... |
| | | } |
| | | ``` |
| | | |
| | | #### Setup Window Components |
| | | |
| | | Then you can use `QWindowKit` data types and classes by importing it's URI: |
| | | |
| | |
| | | |
| | | You can omit the version number or use "auto" instead of "1.0" for the module URI if you are using Qt6. |
| | | |
| | | #### Window Attributes (Experimental) |
| | | |
| | | TODO |
| | | |
| | | ### Learn More |
| | | |
| | | See [examples](examples) for more demo use cases. The examples have no High DPI support. |