You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
621b2e1cde
Even though the frame geometry and the client geometry have a connection between themselves, it doesn't mean that the frame geometry will change if the client geometry has changed and vice versa. For example, it can be the case when the border size changes. The frame geometry won't change, but the client geometry will. In general, similar to the frameGeometryChanged signal, we need another signal that is emitted when the client geometry has been changed that can be used then in DecoratedClientImpl. Unfortunately, 5.19 release is around the corner and I would prefer not to do any geometry-related changes in order to avoid introducing new regressions. In order to fix the propagation of the client size to decorations, this change ports DecoratedClientImpl from frameGeometryChanged to a signal that is emitted whenever geometry of any kind has been changed. BUG: 419080 FIXED-IN: 5.19.0 |
4 years ago | |
|---|---|---|
| .. | ||
| decoratedclient.cpp | 4 years ago | |
| decoratedclient.h | ||
| decorationbridge.cpp | ||
| decorationbridge.h | ||
| decorationpalette.cpp | ||
| decorationpalette.h | ||
| decorationrenderer.cpp | ||
| decorationrenderer.h | ||
| decorations_logging.cpp | ||
| decorations_logging.h | ||
| settings.cpp | ||
| settings.h | ||