diff options
Diffstat (limited to 'kde-frameworks/plasma/files')
2 files changed, 0 insertions, 88 deletions
diff --git a/kde-frameworks/plasma/files/plasma-5.102.0-fix-calc-of-distance-betw-dialog-and-parent-applet.patch b/kde-frameworks/plasma/files/plasma-5.102.0-fix-calc-of-distance-betw-dialog-and-parent-applet.patch deleted file mode 100644 index 13f7a7e20232..000000000000 --- a/kde-frameworks/plasma/files/plasma-5.102.0-fix-calc-of-distance-betw-dialog-and-parent-applet.patch +++ /dev/null @@ -1,44 +0,0 @@ -From 1e0042c750756d0963d11d125978f47ea830d495 Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Niccol=C3=B2=20Venerandi?= <niccolo@venerandi.com> -Date: Tue, 31 Jan 2023 20:25:06 +0000 -Subject: [PATCH] Dialog: Fix calculation of distance between dialog and parent - applet - -`ParentRect` is not using the same coordinate system as `dialogPos` and `avail`, -which could result in incorrect placement of dialogs when you have e.g. multiple -monitors or a non-maximized panel. This replaces `ParentRect` with `dialogPos` so -the coordinate systems remain in sync. - -BUG:464201 -BUG:464513 -FIXED-IN: 5.103 - - -(cherry picked from commit eda6caabcffff484544af8949d0ca0a3ea3ce333) ---- - src/plasmaquick/dialog.cpp | 4 ++-- - 1 file changed, 2 insertions(+), 2 deletions(-) - -diff --git a/src/plasmaquick/dialog.cpp b/src/plasmaquick/dialog.cpp -index 786d7ebe2..bdbdd028b 100644 ---- a/src/plasmaquick/dialog.cpp -+++ b/src/plasmaquick/dialog.cpp -@@ -1249,13 +1249,13 @@ QPoint Dialog::popupPosition(QQuickItem *item, const QSize &size) - switch (d->location) { - case Plasma::Types::TopEdge: - case Plasma::Types::BottomEdge: -- if (qAbs(parentRect.center().x() - avail.center().x() ) < size.width() / 2 - parentRect.width() / 3) { -+ if (qAbs(dialogPos.x() + size.width() / 2 - avail.center().x() ) < size.width() / 2 - parentRect.width() / 3) { - dialogPos.setX(avail.center().x() - size.width() / 2); - } - break; - case Plasma::Types::LeftEdge: - case Plasma::Types::RightEdge: -- if (qAbs(parentRect.center().y() - avail.center().y() ) < size.height() / 2 - parentRect.height() / 3) { -+ if (qAbs(dialogPos.y() + size.height() / 2 - avail.center().y() ) < size.height() / 2 - parentRect.height() / 3) { - dialogPos.setY(avail.center().y() - size.height() / 2); - } - break; --- -GitLab - diff --git a/kde-frameworks/plasma/files/plasma-5.102.0-fix-flicker-on-fade-animation.patch b/kde-frameworks/plasma/files/plasma-5.102.0-fix-flicker-on-fade-animation.patch deleted file mode 100644 index 1c6ddab618aa..000000000000 --- a/kde-frameworks/plasma/files/plasma-5.102.0-fix-flicker-on-fade-animation.patch +++ /dev/null @@ -1,44 +0,0 @@ -From 3fcd43a6ed03d0aff188dfc190cc464c34302a1f Mon Sep 17 00:00:00 2001 -From: Arjen Hiemstra <ahiemstra@heimr.nl> -Date: Tue, 10 Jan 2023 12:46:20 +0100 -Subject: [PATCH] iconitem: Adjust fade animation to not flicker as much - -As it turns out, mix(old texture, new texture, animation value) does -actually result in a different visual from simply blending the two -textures on top of each other, because the old texture first gets -blended with the underlying color. This results in some of the -underlying color bleeding through, which can cause flickering if the two -textures are almost the same. To avoid this, change the animation -slightly so that rather than crossfading, we first fade in the new -texture then fade out the old texture. This doesn't cause a whole lot of -visual difference for two completely different textures, but removes the -flickering when they are very similar. - -BUG: 463061 -BUG: 463685 ---- - src/declarativeimports/core/iconitem.cpp | 8 ++++++-- - 1 file changed, 6 insertions(+), 2 deletions(-) - -diff --git a/src/declarativeimports/core/iconitem.cpp b/src/declarativeimports/core/iconitem.cpp -index de1f56c69..a474a72f9 100644 ---- a/src/declarativeimports/core/iconitem.cpp -+++ b/src/declarativeimports/core/iconitem.cpp -@@ -645,8 +645,12 @@ QSGNode *IconItem::updatePaintNode(QSGNode *oldNode, UpdatePaintNodeData *update - m_textureChanged = true; - } - -- updateSubtree(oldNode->firstChild(), 1.0 - m_animValue); -- updateSubtree(oldNode->lastChild(), m_animValue); -+ // Rather than doing a perfect crossfade, first fade in the new texture -+ // then fade out the old texture. This is done to avoid the underlying -+ // color bleeding through when both textures are at ~0.5 opacity, which -+ // causes flickering if the two textures are very similar. -+ updateSubtree(oldNode->firstChild(), 2.0 - m_animValue * 2.0); -+ updateSubtree(oldNode->lastChild(), m_animValue * 2.0); - } else { - if (oldNode->childCount() == 0) { - oldNode->appendChildNode(createSubtree(1.0)); --- -GitLab - |