qt-mobility

[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?

[wysota]

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?

From usability point of view, in most cases yes. Usually you're only interested in the upcoming segment. When you are traveling it, you can update the route and get instructions for the next segment. There is a high chance you will never reach the destination of your route so why generate (and transmit) textual description for it?

If you want instructions for all segments upfront, you have to use a source that will give them to you or convince the source you are currently using to do it. Bearing the fact that you are using a limited free service, there is a chance that if you pay for the service, you will get richer results.