Thread: Chinese 2 DIN radio/GPS, will not exit GPS mode

Originally Posted by osiris4isis

I was wondering about that as well; but I think if the keycode of the button pressed can be determined, then proggy might be able to be config to do something with it. This is why I asked the proggy to be run and keycode collected.

My understanding with the keycodes (and associated [keybind] section in sys.txt/device .ini files) was that they allow you to "program" a 2DIN hardware key to perform an iGo software function (so that, for example, you can program a hardware key to bring up the Primo "Find" dialog). In this case, we need to initiate a 2DIN function though (to switch back to the main 2DIN interface), so I'm not sure how the key binding can help in this case - unless I'm just not understanding the approach you are taking with the keybindings.

In other words, I was under the impression that setting up keybindings in iGo just allows us to map a software function to a hardware key - not map a hardware function to a hardware key. If that makes sense... :-) At least not without a version of Primo that is customized to this specific hardware.

In my mind, the real issue here is that the 2DIN is not allowing us to switch between 2DIN and Navi functions. As far as I can tell, Primo itself is operating 100% correctly and there is nothing to "fix" on the Primo side.

Just thinking out loud....

Sent from my Vi10 Plus using Tapatalk

Originally Posted by osiris4isis

The objective is to make proggy does something if hardware key is pressed (at least that's what I thought it is.) There is an event to minimize proggy which might get him back to main menu of nav unit (not proggy) So if we can find the keycode of a key and bind to that event, it should do it.

The problem is that the iGo Minimize function doesn't work either (it does the same thing that the Exit function does). From an earlier post:

"Jtrosky there is a minimize button but when I click on it the button turns yellow and nothing happens, it goes no where..."

So whether he minimizes Primo with the software button or a hardware button, I don't think that the result will be any different (but I could be wrong). it seems to me that the Primo software is cut off from the rest of the 2DIN system at the OS level (like it is on my Rosen GM1010). With the Rosen, even if I run a task manager on the Navi "side", there are no other processes running - it runs in it's own dedicated WinCE OS. I have a feeling that his Navigation function is completely self-contained like it is on my Rosen - which would require a way to switch between 2DIN and Navi functions (controlled by the 2DIN, not Primo). But we can't seem to get that to happen...

I'm at a loss for where to go from here...

Sent from my Vi10 Plus using Tapatalk