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

[Question]: How to be smoother when i'm displaying my marker in driver mode? #1492

Closed
3 of 8 tasks
Naografix opened this issue Apr 25, 2024 · 3 comments
Closed
3 of 8 tasks
Labels
status: closed (missing info) Indicates the issue was automatically closed due to a lack of information. status: needs more info We need more information before we can continue work on this issue.

Comments

@Naografix
Copy link

Please check the following before submitting a new issue.

Please select for which platform(s) you need help

  • Android
  • iOS
  • Linux
  • macOS
  • Web
  • Windows

Your question

I'd like to know how to get a more natural version of my marker's movement.

Here are two examples:

Here, my version of flutter map + geolocator + marker
slow

Here a smooth version of OsmAnd app with the same route:
smooth

How can I make moving the marker more natural? I'm using the Geolocator stream, but it refreshes every 3-5 seconds.
Thanks

Version

last

@MohdSaadi
Copy link

MohdSaadi commented Jul 17, 2024

@Naografix
any updates ?
i have set the geolocator stream to update the marker every 1 second but like your problem the maker transition its not smooth

@TimHoogstrate
Copy link
Contributor

Dear @Naografix,

Please share your AndroidSettings or LocaitionSettings to see if you can make any improvements. Try to play around with the settings to see if you have a different result.

Kind regards

@TimHoogstrate TimHoogstrate added the status: needs more info We need more information before we can continue work on this issue. label Aug 20, 2024
Copy link

github-actions bot commented Sep 3, 2024

Without additional information, we are unfortunately not able to resolve this issue. Therefore, we reluctantly closed this issue for now. If you run into this issue later, feel free to file a new issue with a reference to this issue. Add a description of detailed steps to reproduce, expected and current behaviour, logs and the output of 'flutter doctor -v'. Thanks for your contribution.

@github-actions github-actions bot added the status: closed (missing info) Indicates the issue was automatically closed due to a lack of information. label Sep 3, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: closed (missing info) Indicates the issue was automatically closed due to a lack of information. status: needs more info We need more information before we can continue work on this issue.
Projects
None yet
Development

No branches or pull requests

3 participants