-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Grey bar is not visible in GeoPoint widget when user opens widget again with saved location #2857
Comments
@opendatakit-bot claim |
@mmarciniak90 As I understand it, the disappearance of the grey bar is intentional and by design. The bar says "Long press to place mark...". When there exists a saved location, the user cannot long-press to place a mark, so the instruction is not shown. After the user deletes the saved location, it is then possible again to long-press to place a mark, so the instruction is shown. Can you help me understand why you consider this to be a bug? |
The behavior of OSM and the Google Map are inconsistent, the OSM has the bar but the Google Map has not. So I guess this is the reason why @mmarciniak90 consider it as a bug. @zestyping |
@huangyz0918 Thank you for explaining, I understand. This issue is obsolete now because the Google Maps activity and the OSM activity have been merged into a single activity after 1.17, so they now have the same behaviour. The change in the user-visible behaviour of this grey bar is noted in the description of #2776, the PR that merges the two activities into one activity, where it says:
|
@zestyping Thanks for explaining! So this issue is obsolete and should be closed. @mmarciniak90 , and I shall close #2859 too. |
Software and hardware versions
Collect v1.17, older versions were not be verified
Google Maps
Problem description
Grey bar is not visible in GeoPoint widget when user opens widget again with saved location
Steps to reproduce the problem
Expected behavior
Other information
Discovered while testing #2806
The text was updated successfully, but these errors were encountered: