Skip to content
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

on the first run blue location dot is not displayed #318

Closed
matkoniecz opened this issue Jun 12, 2017 · 6 comments
Closed

on the first run blue location dot is not displayed #318

matkoniecz opened this issue Jun 12, 2017 · 6 comments
Labels

Comments

@matkoniecz
Copy link
Member

matkoniecz commented Jun 12, 2017

To reproduce: uninstall app, install again (either via adb or from store)

screenshot_2017-06-12-20-48-34-441_de westnordost streetcomplete

@Binnette
Copy link
Contributor

Binnette commented Jun 12, 2017

👍 I encounter this bug many times... But i was too lazy to report it or try fix it thanks ! 😅
On my phone, it happens sometimes when i run the app (and not only after install). When it happens, i'm used to close the app, and run it again.

  • Android : 6.0
  • Device : Homtom HT17 Pro
  • SC : 6f90a23

@westnordost
Copy link
Member

Interestingly the accuracy circle is, even though they are created the same way. Only difference:

locationMarker.setStylingFromString("{ style: 'points', color: 'white', size: ["+TextUtils.join(",",sizeInDp(dot))+"], order: 2000, flat: true, collide: false }");
is set immediately once and then not again (as opposed to the accuracy circle, which updates all the time).

This will be a tangram-es issue. When you create a bug report, add your Android version, device etc., as usual.

@matkoniecz
Copy link
Member Author

In my case it is

Device (Manufacturer and Model) - Redmi 4 Xiaomi
Android Version - 6.0.1 MMB29M

(I have not created tangram-es issue as I have no idea what happens here and would prefer to understand it before reporting bugs)

@westnordost
Copy link
Member

But you reported a bug!

@matkoniecz
Copy link
Member Author

It was "something is wrong with SC" and it was quite easy to check that the SC is wrong (rather than a bug introduced by my own changes). But I would prefer to understand how tangram-es is used before reporting it as a tangram-es bug.

@westnordost
Copy link
Member

So, what about this? I can't reproduce this on my phone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants