While Odyssey Navigator looks good on my touch-screen keyboard-free ASUS R2h UMPC, many people like netbooks for their flexibility and low cost. Unfortunately, I don't see any keyboard shortcuts for using this program with a netbook. Am I missing something?
Terry
Terry
This is an expansion of the question Terry asked.
I installed Odyssey Navigator on my Acer Aspire One netbook and I can't find any way to use the keyboard with it.
In general, my first impressions are very favorable when comparing it to other similar nav programs like Garmin Mobile PC, iNav's iGuidance and Geolife's Navmii.
But I find the lack of keyboard support a never-ending source of frustration. It started when I had to enter the registration key. That's a really long string of numbers and letters. Not only was I forced to use the mouse to enter it all through the onscreen keyboard, the onscreen keyboard requires that you keep flipping between the alpha and numeric screens. By the time I got the entire string entered correctly I was about ready to throw the netbook out the window.
It's similarly annoying when searching. I've only been testing in a static configuration in the house so far, so I have the option of using the mouse. I won't have that option in a vehicle. Using the touchpad in the netbook will make it an even bigger exercise in frustration.
As Terry mentioned, there do not appear to be any keyboard shortcuts for such things as moving between and within menus, selecting menu items or even just simple things like zooming and panning the map screen.
On a non-touchscreen device this is really frustrating. Are we missing something? Is there a way to use the keyboard and we're just not looking in the right place?
Sorry to jump on such a negative aspect right away, but this was the very first thing I encountered when I fired up Odyssey Navigator and it continues to be a frustration every time I use it. The apparent lack of any keyboard shortcut for zooming is a particular frustration because the + and - icons for zooming are not always available on the map screen. Without them you're stuck if you need to zoom, and I haven't used it enough to always remember how to get them to reappear. I end up stumbling around clicking things until they come back ... sometimes with other junk I didn't want.
...ken...
I installed Odyssey Navigator on my Acer Aspire One netbook and I can't find any way to use the keyboard with it.
In general, my first impressions are very favorable when comparing it to other similar nav programs like Garmin Mobile PC, iNav's iGuidance and Geolife's Navmii.
But I find the lack of keyboard support a never-ending source of frustration. It started when I had to enter the registration key. That's a really long string of numbers and letters. Not only was I forced to use the mouse to enter it all through the onscreen keyboard, the onscreen keyboard requires that you keep flipping between the alpha and numeric screens. By the time I got the entire string entered correctly I was about ready to throw the netbook out the window.
It's similarly annoying when searching. I've only been testing in a static configuration in the house so far, so I have the option of using the mouse. I won't have that option in a vehicle. Using the touchpad in the netbook will make it an even bigger exercise in frustration.
As Terry mentioned, there do not appear to be any keyboard shortcuts for such things as moving between and within menus, selecting menu items or even just simple things like zooming and panning the map screen.
On a non-touchscreen device this is really frustrating. Are we missing something? Is there a way to use the keyboard and we're just not looking in the right place?
Sorry to jump on such a negative aspect right away, but this was the very first thing I encountered when I fired up Odyssey Navigator and it continues to be a frustration every time I use it. The apparent lack of any keyboard shortcut for zooming is a particular frustration because the + and - icons for zooming are not always available on the map screen. Without them you're stuck if you need to zoom, and I haven't used it enough to always remember how to get them to reappear. I end up stumbling around clicking things until they come back ... sometimes with other junk I didn't want.
...ken...
I agree with Terry & Ken. Keyboard shortcuts would help those with keyboards. And please make it possible to enter destination addresses via keyboards (for those with out touch screens). It is time consuming to try entering anything by mouse clicking on the OSK (on-screen keyboard).
By the way, the OSK is wonderful, and I love the predictive typing feature! Nicely done! I'm using a 12 inch screen, but I bet even on a much much smaller touch screen the OSK, as well as the whole application, is very comfortable to use.
By the way, the OSK is wonderful, and I love the predictive typing feature! Nicely done! I'm using a 12 inch screen, but I bet even on a much much smaller touch screen the OSK, as well as the whole application, is very comfortable to use.
I second Marvin's comments about the onscreen keyboard. Clearly a lot of thought has gone into making it really easy to use. I want to apologize if anyone thinks my initial post about it is a knock on it. It's not.
Garmin and others could sure take a lesson from the onscreen keyboard in Odyssey Navigator (Garmin doesn't even have one in Mobile PC so you're in trouble if you are using a touchscreen-only device.)
...ken...
Garmin and others could sure take a lesson from the onscreen keyboard in Odyssey Navigator (Garmin doesn't even have one in Mobile PC so you're in trouble if you are using a touchscreen-only device.)
...ken...
There seem to be some keyboard shortcuts. I noticed in a couple of menu windows I was able to go back one level by hitting the ESC-key. But that's clearly not enough to keep netbook and laptop users very happy.
Hi Guys,
I think in one of the earlier discussions with Marvin I had explained we only have 1 stream of code for Odyssey, and that stream is intended for PND devices. As such it is touch screen based, and no keyboard input is coded in simply as it would increase the costs to maintain 2 code development streams.
While ON is for PND, and other WinCE devices (1 and 2 DIN car stereo/GPS/TV units) the port for Windows and Linux was available and we jumped on the chance to provide a low cost Nav option for these platforms, particularly here in Australia where there is simply nothing else current and less that $250. A side effect was we had to keep the code streams the same, at least initially.
In Australia a lot of our sales go to those with in-car PCs, and so have touch screens, thus it is not an issue. However, in saying all that, I have taken on board all your comments regarding the keyboard, and will again see if we can cost-effectively split the code stream off in future releases. If the cost/benefit curve (now that we have possible markets outside Australia) is favorable, we will commission the the enhancement. But as you say, at least it is predictive which reduces the pain!
I think in one of the earlier discussions with Marvin I had explained we only have 1 stream of code for Odyssey, and that stream is intended for PND devices. As such it is touch screen based, and no keyboard input is coded in simply as it would increase the costs to maintain 2 code development streams.
While ON is for PND, and other WinCE devices (1 and 2 DIN car stereo/GPS/TV units) the port for Windows and Linux was available and we jumped on the chance to provide a low cost Nav option for these platforms, particularly here in Australia where there is simply nothing else current and less that $250. A side effect was we had to keep the code streams the same, at least initially.
In Australia a lot of our sales go to those with in-car PCs, and so have touch screens, thus it is not an issue. However, in saying all that, I have taken on board all your comments regarding the keyboard, and will again see if we can cost-effectively split the code stream off in future releases. If the cost/benefit curve (now that we have possible markets outside Australia) is favorable, we will commission the the enhancement. But as you say, at least it is predictive which reduces the pain!
Even with the greyed out letters, I find the ABC keyboard a real pain to use. How about a QWERTY option as well. There is certainly room by removing the non-used character set switch as you choose the language elsewhere anyway.
And how come the ampersand is greyed out in the 123 set. How can I route to A&W!!
Terry
And how come the ampersand is greyed out in the 123 set. How can I route to A&W!!
Terry
Mal,
This can't be a rewrite of Odyssey Mobile as there is a City not first option in that product. I saw it when searching for a manual. What is the product this is a stream of?
Terry
This can't be a rewrite of Odyssey Mobile as there is a City not first option in that product. I saw it when searching for a manual. What is the product this is a stream of?
Terry
Terry,
You are right, it is not a re-write of "Odyssey Mobile" at all, and not related whatsoever.
I am just loading Canada maps now (as we don't have A&W here is Oz) to have a look.
You are right, it is not a re-write of "Odyssey Mobile" at all, and not related whatsoever.
I am just loading Canada maps now (as we don't have A&W here is Oz) to have a look.
Sorry, there are some short cuts, but not for entering the names etc...
The shortcuts that are there are,
Up Arrow
Down Arrow
Left Arrow
Right Arrow
Enter (Enter/OK)
Escape (Back)
Space (Main Menu)
Backspace (Find Menu)
F2 (Zoom map In)
F1 (Zoom map Out)
F3 (Lock Map position)
F4 (Change Heading View in map view)
The shortcuts that are there are,
Up Arrow
Down Arrow
Left Arrow
Right Arrow
Enter (Enter/OK)
Escape (Back)
Space (Main Menu)
Backspace (Find Menu)
F2 (Zoom map In)
F1 (Zoom map Out)
F3 (Lock Map position)
F4 (Change Heading View in map view)
Those will come very handy, Mal. Thanks! If these shortcuts have been put into the app, chances are good more could be added in future releases.
Quote:
|
Originally Posted by Malster Terry, I am just loading Canada maps now (as we don't have A&W here is Oz) to have a look. |
What? no A&W in Oz! I don't think its that big in US any more; certainly not on the west coast anyway.
Terry
Quote:
|
Originally Posted by Malster Sorry, there are some short cuts, but not for entering the names etc... The shortcuts that are there are, ... {snip} ... |
Do the arrow keys and Enter work on the menus? .... Ah, I'll try that out myself tonite.
...ken...
Hi Ken, Yes the arrow keys do work in moving the highlighted key (letter)... Then use Enter to select it.
1. Using the arrow keys does not allow access to the "Find & Go" option on the main menu. You can use either the up and down arrows or the left and right arrows to cycle through all the other selections on the main menu page but not "Find & Go".
Ooops, forget that. Confusion because of the different colours used for highlighting selections.
When I hover the mouse over any selection on any menu page, the button under the mouse cursor turns green.
When I use the arrow keys to cycle through the buttons on any menu page, the selected button turns orange.
So, in the example above, the mouse cursor just happened to be hovering over the "Find & Go" button. As I poked the arrow keys to cycle through the main menu selections, whenever the selection should have highlighted the "Find & Go selection" it didn't.
That is, when the button should have turned orange because I got there using the arrow keys, it stayed green (because the mouse cursor happened to be hanging over it, even though I wasn't actually using the mouse). So it behaved just as if the arrow selection had "disappeared". That is, there were no orange buttons on the screen at all.
Recommendation to make it easier for non-touchscreen use. When someone uses the arrow keys for navigation on ANY menu page, don't use a different colour. That is, only use green (or orange) to indicate the selected button, regardless if I'm moving the mouse or poking the arrow keys. In either case I just want to know which function is currently selected so show me with a single colour.
If that is not possible, or too difficult to consider, then please turn off the other colour. That is, if a button is selected due to the mouse cursor position and is green, as soon as I start cycling through the buttons with the arrow keys, turn OFF the green button so it can turn orange when I get there with the arrow keys.
The current method of using two different colours simultaneouly is confusing.
I hope that makes sense.
...ken...
Ooops, forget that. Confusion because of the different colours used for highlighting selections.
When I hover the mouse over any selection on any menu page, the button under the mouse cursor turns green.
When I use the arrow keys to cycle through the buttons on any menu page, the selected button turns orange.
So, in the example above, the mouse cursor just happened to be hovering over the "Find & Go" button. As I poked the arrow keys to cycle through the main menu selections, whenever the selection should have highlighted the "Find & Go selection" it didn't.
That is, when the button should have turned orange because I got there using the arrow keys, it stayed green (because the mouse cursor happened to be hanging over it, even though I wasn't actually using the mouse). So it behaved just as if the arrow selection had "disappeared". That is, there were no orange buttons on the screen at all.
Recommendation to make it easier for non-touchscreen use. When someone uses the arrow keys for navigation on ANY menu page, don't use a different colour. That is, only use green (or orange) to indicate the selected button, regardless if I'm moving the mouse or poking the arrow keys. In either case I just want to know which function is currently selected so show me with a single colour.
If that is not possible, or too difficult to consider, then please turn off the other colour. That is, if a button is selected due to the mouse cursor position and is green, as soon as I start cycling through the buttons with the arrow keys, turn OFF the green button so it can turn orange when I get there with the arrow keys.
The current method of using two different colours simultaneouly is confusing.
I hope that makes sense.
...ken...
Similar Topics: