Open lains opened 5 years ago
What graphics system was this observed on? Drawing the cursor / drawing a layer is highly graphics dependent. #817 may fix something looking different on cursors with too small layer. But here it was observed with a simple circle. Here #817 most probably doesn't fix it.
The screenshot above was taken on a device running Navit on Android. From the display, I assume the layout was "Bike" I'm guessing that this likely happens more often when moving slowly (walking) and for sure, when map is not redrawn each time (thus not in follow vehicle mode, but in map browse mode).
OK, I don't have any Android device to check on android. But usually the map in the background including the highlighted route is not redrawn unless dragged around or the cursor leaves the screen. So the highlighted route not being updated is quite OK.
The cursor is draw within it's own layer which is moved on top of the map. This layer has it's own drawing context and is usually transparent except the drawn cursor. So the artefacts are most probably because the transparent layer is not cleaned properly by the graphics back end on re draw. If using a small zoom level, the cursor is only moved few pixels per GPS refresh and the border might wipe away artefacts. On high zoom level the cursor "jumps" some distance between the GPS updates and therefore the next location doesn't overlap and the "wiping" effect vanishes.
Another thing that could cause this is the cursor layout. If the "layer" size of the cursor is too small such artefacts could happen (on android, not on Qt5) as well.
On Sailfish / Qt5 I don't get any artefacts from cursor drawing, but I know I once had such a bug in Qt5 graphics as well.
When navigating, if follow vehicle is dectivated, the current route followed is not removed from the map as the vehicle cursor progresses and there are glitches also on moving the cursor itself (when the vehicle speed is low).
Steps to reproduce:
The screenshot below illustrates this problem.
This is not a blocking issue, as there are ways to work around it (moving the map actually forces redrawing and cleans up the view). This issue has been there for a while, but it was reproduced on https://github.com/navit-gps/navit/commit/845dd4092ee64bbce0939299793336decafa40b8