Skip to content

Fix/issue 94 double tap lock fix#97

Merged
luantak merged 2 commits intoluantak:masterfrom
Rage0fKratos:fix/Issue-94-double-tap-lock-fix
Apr 30, 2026
Merged

Fix/issue 94 double tap lock fix#97
luantak merged 2 commits intoluantak:masterfrom
Rage0fKratos:fix/Issue-94-double-tap-lock-fix

Conversation

@Rage0fKratos
Copy link
Copy Markdown
Contributor

Fix: Double-tap to lock not working outside central area

#94

Issue:
Double-tap to lock was only working within a specific central region. Taps on margins, padding, or gaps between widgets were ignored.

Root cause:
Gesture listener was attached to a limited view instead of the full root container.

Fix:
Moved the double-tap gesture listener to the root container view.
This enables detection across all non-interactive areas while preserving widget/icon interactions.

Behavior after fix:

  • Double-tap works on empty areas across the screen
  • Widgets and icons continue to handle their own touch events
  • No interference with click/scroll behavior (observed)

Tested on:

  • Environment: Android Emulator
  • API level: [37]
  • Device profile: [Pixel 9a]

Scenarios tested:

  • Empty area → lock triggered
  • App icon → opens normally
  • Widget → interaction unaffected

Limitations:

  • Not yet validated on a physical device (touch latency and gesture detection may differ)

Notes:
If any views consume touch events unexpectedly, additional handling may be required.

Moved the double-tap gesture listener from a specific middle band to the root container. This ensures that tapping any unoccupied area (margins, padding, or gaps between widgets) triggers the lock, while still allowing widgets and icons to handle their own interactions.
@luantak luantak merged commit 263ad9d into luantak:master Apr 30, 2026
2 checks passed
@luantak
Copy link
Copy Markdown
Owner

luantak commented Apr 30, 2026

@Rage0fKratos works well thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants