Don't use hover effects when on mobile

[johnny9]

[jarolrod]

Working well, TextButton is still showing a stuck state

[johnny9]

from 6b1c0c0 to 110afe0

• rebased with main

[johnny9]

@jarolrod I'm not able to reproduce the issue with the TextButton

[jarolrod]

@johnny9 Press it, hold it, then let go somewhere else on the screen

[johnny9]

I think the apk maybe isn't updating from CI

[jarolrod]

Still seeing the issue with the TextButton, I believe this is because there is no "DEFAULT" state to return to after the "PRESSED" state on Android; and we don't see this issue on desktop so must be some API difference related to Android causing the UI issue.

something along the lines of this should do:

diff --git a/src/qml/controls/TextButton.qml b/src/qml/controls/TextButton.qml
index 0bfafecde..2d8bcf779 100644
--- a/src/qml/controls/TextButton.qml
+++ b/src/qml/controls/TextButton.qml
@@ -39,6 +39,14 @@ Button {
         }
     }
     states: [
+        State {
+            name: "DEFAULT"; when: !root.pressed && !root.hovered
+            PropertyChanges {
+                target: root
+                textColor: root.textColor
+                bgColor: root.bgColor
+            }
+        },
         State {
             name: "PRESSED"; when: root.pressed
             PropertyChanges {

[johnny9]

update from 110afe0 to 405a5c8:

• rebased with main

[jarolrod]

ACK 405a5c8

After the recent rebase, CI is building artifacts again, and this PR now works perfectly.