From d2d2e3af3d7bd292bb6dee7ff2f50a36dcefb0ea Mon Sep 17 00:00:00 2001 From: Murillo Bernardes Date: Sun, 13 May 2018 15:39:26 +0200 Subject: mobile: prevent Action buttons hijack after delete This gets delete dive working properly. Kirigami passive notification ends up hijacking area where the "Add dive" or "Delete" or "Discard" buttons are shown. So after deleting a dive the "Undo" button from the notification keeps handling the touch events even when not visible. Signed-off-by: Murillo Bernardes --- scripts/mobilecomponents.sh | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'scripts') diff --git a/scripts/mobilecomponents.sh b/scripts/mobilecomponents.sh index af93f6281..b30efe385 100755 --- a/scripts/mobilecomponents.sh +++ b/scripts/mobilecomponents.sh @@ -80,6 +80,10 @@ sed -i -e "s/visible: root.action/visible: root.action \&\& \!Qt.inputMethod.vis sed -i -e "s/visible: root.leftAction/visible: root.leftAction \&\& \!Qt.inputMethod.visible/g" src/controls/private/ActionButton.qml sed -i -e "s/visible: root.rightAction/visible: root.rightAction \&\& \!Qt.inputMethod.visible/g" src/controls/private/ActionButton.qml +# kirigami hack: passive notification hijacks area even after disabled. +# https://bugs.kde.org/show_bug.cgi?id=394204 +sed -i -e "s/width: backgroundRect/enabled: root.enabled; width: backgroundRect/g" src/controls/templates/private/PassiveNotification.qml + # another hack. Do not include the Kirigami resources (on static build). It causes # double defined symbols in our setting. I would like a nicer fix for this # issue, but failed to find one. For example, not adding the resource in -- cgit v1.2.3-70-g09d2