Hi, I remembrer the QtWS22 mention "Modernize styles". In the modernize style,
more and more platforms have begun to support adding blurred areas to windows.
Although the specific blurring effects are different, but they have similar
behaviors and APIs, so we can add APIs to QWindow to allow the
This case is very complicated. In actual we often expect to get an
app_compile_version with the smallest version number. In the above case, it
should be 6.3, but the existing code cannot do it. If we have a better way then
we can rewrite it, but the current implementation should be removed anyw
This is a good idea, we need a similar approach also in our projects, but
QCoreApplicationPrivate::app_compile_version is not perfect, it is only valid
after constructing QCoreApplication, I think we should change a better way to
get a valid one at any time app_compile_version. I have an idea: w
I written a patch: https://codereview.qt-project.org/c/qt/qtbase/+/414909 .
Although it's only a draft, but it already has the core functionality, it works
fine in my tests, and I think it's a reasonable solution.
发件人: Development 代表 Zhang JiDe
发送时间
I agree that we should fix this, but it's not as simple as passing the
mouseReleaseEvent to the QPushButton, but we should make sure that for a
QWidget, whatever happens, the mouse press and release are paired, always
notify the mouse release to the QWidget of pressed target. If adding a new
ev
The mention of VNC in damage tracking is just one example, since the frame is
encoded, it removes the duplication between the two frames, so I'm not sure how
much help by providing damage tracking for VNC, but that once know the damaged
area, it will be possible to reduce the amount of data read
For a example:
WaylandOutput {
WaylandClientSurface {
...
}
Button {
...
}
}
In the WaylandOutput, its have two item. The first item is a
WaylandClientSurface, its will report the damaged area of the surface to
wayland compositor from the wayland client when the
