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

Drawing exact ahead path in navigation mode #1338

Open
Dizzy55 opened this issue Oct 13, 2022 · 3 comments
Open

Drawing exact ahead path in navigation mode #1338

Dizzy55 opened this issue Oct 13, 2022 · 3 comments
Labels
bug For issues that describe a bug renderer For issues in the content of the rendering engine

Comments

@Dizzy55
Copy link

Dizzy55 commented Oct 13, 2022

I draw ahead path in navigation mode. For this purpose I have used signal from "NavigationModel". Here is my code

    Connections {
        target: Navigation.navigationModel
        onRouteAheadChanged: {
            map.addOverlayObject(0, Navigation.navigationModel.routeWayAhead)
        }
    }

But I see strange ways on my screen. Sometimes "routeWayAhead" is longer than needed and my position marker is on it. In this situation user see a tail after marker
inside

Sometimes "routeWayAhead" is shorter than necessary and my position marker is outside of the way
outside

Is it a way to draw exact path for navigation?

@Dizzy55
Copy link
Author

Dizzy55 commented Oct 18, 2022

Moreover, redrawing the path takes a long time and the marker runs into the path anyway. Does engine have a way to draw ahead path fast like a drawing marker?
Thanks in advance

@Framstag Framstag added the renderer For issues in the content of the rendering engine label Apr 2, 2023
@Framstag
Copy link
Owner

Framstag commented Apr 2, 2023

@Karry : This sound a problem in the Qt part? Is @Dizzy55 using the code as designed? I assume that the "way ahead"...

  • Is the complete way ahead and not clipped to the visible area?
  • Is the way in relation to OSM nodes. Especially for the start node. Sounds like the first node must not be the first route node for the rest of the way but the current geo location (at least, if one is "on the way")?

@Framstag Framstag added the bug For issues that describe a bug label Apr 2, 2023
@Karry
Copy link
Collaborator

Karry commented Apr 2, 2023

Yes, this problem is specific for Qt library. Problem is that the route is rendered by map renderer, and rendering may take several seconds. So the route not refreshed with every position update on purpose...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug For issues that describe a bug renderer For issues in the content of the rendering engine
Projects
None yet
Development

No branches or pull requests

3 participants