RBEmerson
03-26-2006, 09:38 PM
I've used various GPSR's for some time and then I met the iQue. Frankly, very early on, I gave up on it as being a pain to use and seriously limited. What does "gave up" mean? Can you say "eBay auction"? Yeah, that "gave up".
And then I RTFM a little closer and found that, well, golly, yes, it does support via points. After getting used to MapSource (is it just me or does the MapSource map never scroll when trying to set a via point that's not immediately visible? And if it's not just me, whyinheck has this been allowed to happen up through V6.10.xx???), using the iQue routing tool seemed just flat broken.
When I stopped trying to do everything in "well, that's how it's done with MapSource" mode, things got easier. But one trick elluded me: extending a route. Not too surprisingly, much of my driving follows a few routes until I branch out further down the road. And queRoutes has some odd notions about a few roads around here, so I have to lay down about 3-4 via points every time I do a route. Wouldn't it be nice to have a couple of "get out of Dodge" routes to get past the same old construction, etc. and extend them to a new destination?
The answer is so simple it plumb evaded me... make the new destination a via point. Of course that means the route now follows the "get out of Dodge part" through the next to last via point, takes off for the new destination before... oops! coming back to the last "get out of Dodge" via point. Hmmm... what happens if I highlight that new via point (with the new, extended destination) and use the "down arrow" button to re-order the list to move my extended destination to the bottom of the via point list? Answer: my old "get out of Dodge" route now leaves Dodge and moves on to the new destination! I've just extended the route!
To summarize: take an existing route, add a via point using the desired new destination, use the list re-ordering arrow buttons to move the new via (and destination) to the bottom of the via point list.
In general, although I do wonder about some of Garmin's design choices, I find that it's best to approach the iQue as its own working environment and not try to do things as they're done elsewhere.
And then I RTFM a little closer and found that, well, golly, yes, it does support via points. After getting used to MapSource (is it just me or does the MapSource map never scroll when trying to set a via point that's not immediately visible? And if it's not just me, whyinheck has this been allowed to happen up through V6.10.xx???), using the iQue routing tool seemed just flat broken.
When I stopped trying to do everything in "well, that's how it's done with MapSource" mode, things got easier. But one trick elluded me: extending a route. Not too surprisingly, much of my driving follows a few routes until I branch out further down the road. And queRoutes has some odd notions about a few roads around here, so I have to lay down about 3-4 via points every time I do a route. Wouldn't it be nice to have a couple of "get out of Dodge" routes to get past the same old construction, etc. and extend them to a new destination?
The answer is so simple it plumb evaded me... make the new destination a via point. Of course that means the route now follows the "get out of Dodge part" through the next to last via point, takes off for the new destination before... oops! coming back to the last "get out of Dodge" via point. Hmmm... what happens if I highlight that new via point (with the new, extended destination) and use the "down arrow" button to re-order the list to move my extended destination to the bottom of the via point list? Answer: my old "get out of Dodge" route now leaves Dodge and moves on to the new destination! I've just extended the route!
To summarize: take an existing route, add a via point using the desired new destination, use the list re-ordering arrow buttons to move the new via (and destination) to the bottom of the via point list.
In general, although I do wonder about some of Garmin's design choices, I find that it's best to approach the iQue as its own working environment and not try to do things as they're done elsewhere.