I do not get your point, sorry.
The "problem" with "overlapping" instructions on short L/R combinations is not new and I now this behavior from pro version.
At the moment Locus gives us two instructions before a turn. At bike speed its around 80m and 20m before turn.
If a following turn occurs within the 80m after the first turn, you get the first instruction for the second turn before the first turn. And Menion is right. With long instructions its "After x metres turn LEFT and then after y metres turn "RIGHT". With short instructions (beeps) its - .. - T .. T T for turn.
Is that your problem?
If we want to prevent that problem, Menion needs to change the instructions, so no instruction for the second next turn before next turn is finished. Is that your proposal? I would support this for bike (short instructions, beep), not for car.
In the other thread (Navigation generator) we found out, that navigation mode is more suitable for mtb than guiding mode.
We only need strict order for the waypoints. Menion implements that as an option to navigation mode now (thanks again). So we mtb guys will definitly use navigation mode now.
And I testes this "new" bike navigation mode. Here are my findings:
1. Strictly waypoints is really strict ;-). If you don't reach a point, due to unprecise GPS track or bad GPS reception, Locus sticks to the waypoint behind you, although you are going on with the track. In this moments you have to go to next waypoint manually. I see the problem: On the one hand it should be strict, on the other hand intelligent enough to take the next suitable waypoint if you "miss" one. Difficult. Is there a good solution Menion?
2. The modification of screen on/off is not really much better than before. Like I understand Menion, its still "time based". Whenever something goes wrong in timing from first instruction (screen on) to turn, the display is off before the turn. This happens with change of speed and also when you stop before a crossing. Maybe its typical for bike groups, but at 30% of all crossing there is a waiting time before turns. In these cases the screen is off when you want to go on with the track.
Is there a opportunity to make the screen on/off position dependend?
3. I assume the errors (no blue dots, no voice instruction) with manually added instructions will be solved in next versions.
Over all my great thanks to Menion. Its definitely going in the right direction and its fun to test and to help to make it better. I wish I could help you in programming, but I can't.