qt-mobility

[wysota]

No. Simply not each route segment is associated with a maneuver. If there is a road intersection and you are driving straight, you are not making any maneuvers yet you are entering a new route segment.

[untitled]

So how do I get the rest of instructionText()?
I'm sure they do exist and are valid..

[wysota]

This might be the only text the routing server provides.

[untitled]

I don't get it. Every firstRouteSegmen() has a valid maneuver and instructionText(), but the server does not provide the next ones? Semi-implemented functionality?

[wysota]

Check the text, it probably contains the description of the whole route.

[untitled]

Check the text, it probably contains the description of the whole route.

I was checking it with:

qDebug() << segment.maneuver().instructionText();

qDebug() << segment.maneuver().instructionText();

To copy to clipboard, switch view to plain text mode 

and all I got is the first segment before the first maneuver.
Output is for example:

"Head towards Kirkkokatu on Hämeenkatu. Go for 0.4 miles."

"Head towards Kirkkokatu on Hämeenkatu. Go for 0.4 miles."

To copy to clipboard, switch view to plain text mode 

[wysota]

And how complex is the route segment? What is the shape of the segment?

[untitled]

The segment is always a straight way between two maneuvers (turns). I set routes on map by clicking the mouse, I make them pretty easy with 1 turn = 1 maneuver and 2 segments.

[wysota]

So why do you expect more than one text?

[untitled]

Because there are 2 segmenst and get 1 text.
No matter how many segments I make in a route, always 1 text and empty ones after that.
Maybe I'm not getting something in how to retrieve the text or set other segments manyally...

[wysota]

Again, if that's how the source you are using (I'm guessing Navteq) returns the data, there is nothing you can do about it. That's probably how it works to avoid having to generate unnecessary data.

[untitled]

Hm.
I need to show the whole routes instructions. Like:
"Head towards blabla. Go for 0.4 miles"
"Head towards blabla2. Go for 15 miles"
etc..
Is that an unnecessary data?