-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After panning the map several times, the recticle of adding a new feature doesn't move to the right position of the stylus #5296
Comments
@tobiasgrau0 , can you test with APKs here: #5359 -- are you still able to replicate? |
@nirvn : i have tested it with the APK 5359 unfortunately the problem is not solved |
I have the same problem. The stylus works fine until you pan the map and then stops functioning |
I can also confirm the problem in the latest QField version (3.4.3 - Ebo 412c8d). I even updated/ upgraded to the latest hardware (Samsung Galaxy Tab Active 5 5G) and operating system (Android 14, One UI 6.1) to make sure that my ongoing problems with stylus use (unfortunately not just the issue described here) are not due to the outdated base. Regarding the issue discussed here: Maybe this can be a hint for bugfixing, @nirvn? |
Describe the issue
After panning the map several times and add some new points with the stylus, the reticle for adding a new feature don't move to the position of the stylus - the new point feature will be added in a wrong position.
Qfield_problem_.mp4
Reproduction steps
Steps to reproduce the behavior:
Expected behavior
The reticle move to the position of the stylus.
Observed behavior
Sometimes the reticle doesn't move, sometimes it only moves after zooming in and zoom out
Screenshots and GIFs
See video (only a short abstract)
[Please also attach additional files if a specific project/dataset is useful to investigate the problem.]
Additional information
[If the problem happened with QFieldCloud, please add your username and project name.]
The text was updated successfully, but these errors were encountered: