search

rksahu1987 / osmdroid

Automatically exported from code.google.com/p/osmdroid
0 stars 0 forks source link

My location marker position good only while zooming. #423

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Enable myLocation
2. Zoom in/out
3. Move map

What is the expected output? What do you see instead?

While zooming in/out position is correct. Sometimes it stays so until map is 
moved. Then it changes back to wrong position. It should point to same position

What version of the product are you using? On what operating system?
3.0.9 on Android 4.1.2

Please provide any additional information below.

Original issue reported on code.google.com by baneiza...@gmail.com on 24 Apr 2013 at 8:38

Attachments:

GoogleCodeExporter commented 8 years ago 
First and third images were taken while map was zooming. Second one is after it.

Original comment by baneiza...@gmail.com on 24 Apr 2013 at 8:40

GoogleCodeExporter commented 8 years ago 
Do you have hardware acceleration turned off?

Original comment by kurtzm...@gmail.com on 25 Apr 2013 at 1:22

GoogleCodeExporter commented 8 years ago 
Yes. It's strange. It seems that version 3.0.8 doesn't have that bug. But it 
has bug with other custom map icons...

Original comment by baneiza...@gmail.com on 25 Apr 2013 at 2:17

GoogleCodeExporter commented 8 years ago 
Please take a look at the sample application which doesn't have this issue. 
Determine what is different between your application and the sample application 
and report back here.

Original comment by kurtzm...@gmail.com on 26 Apr 2013 at 1:49

GoogleCodeExporter commented 8 years ago 
Just to let you know, this issue is resolved with new version (3.0.10)

Original comment by baneiza...@gmail.com on 2 May 2013 at 12:56

GoogleCodeExporter commented 8 years ago 
Excellent! I still suspect you may have hardware acceleration on - if you can't 
display the compass overlay for example, then you have it on - but either way, 
it's fixed. Thanks for reporting back.

Original comment by kurtzm...@gmail.com on 2 May 2013 at 1:29