Quote Originally Posted by jtrosky View Post
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
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.