This will be a FAQ of sorts. It is a list of problems and solutions that I encountered as I tried to get iGuidance 3.0 properly embedded in RR and the volume working correctly. Hopefully someone will find this post when searching and I might save you from reading this entire thread (all 24 pages of it).
Thread reference here:
http://www.mp3car.com/vbulletin/road-runner/85662-auto-switch-guidance-screen-ig.html
First of all, the implementation can be very easy. As the first post indicates, there is no need to download any beta version of RR. This functionality is built into the regular release of RR now. Just get the latest.
Embedding: (written for iGuidance 3.0)
You will need to use RRConfig and go to the GPS section.
Set “GPS mode” to External (this will generally mean that when you push the GPS menu button in RR the skin “External_gps” will be loaded)
Set “GPS Path” to <full path>\iGuidanceUMPC.exe
Set “GPS window name” to iGuidance
Set “GPS Port” whatever com port your GPS is on. My GPS is on com 4 and I have Xport setup to replicate that to 5,6,7,8. I setup iGuidance to read port 5 and I setup RR to read port 6.
I don’t believe any of the other settings here in the GPS section of the config are making any difference for me. Set them or not, your choice.
Now find these settings at the bottom of the Readme.txt distributed with RR. Read their descriptions. Place these settings in your RR.ini at the bottom and set them appropriately.
ignative=true|false
gpstime=true|false
gpsusadate=true|false
igautosw=true|false
gpsonvoice=true|false
pauseonvoice=true|false
lastscreenswitchtime=[0-30] in seconds.
At this point you should be able to load up RR and click GPS…it should open iGuidance in your skin and iGuidance (w/o window header [which means no menus across top]) will fill the space in that skin allocated to the application.
I am told that if you use ignative=true then you should edit that screen to remove the clipping region. If you use ignative=false then make sure there is a clipping region the same size and position as the application frame.
At this point the problem I had was that I wanted access to the menus that are found on the window header. As I mentioned this window header cannot be seen and it made no difference if I had ignative true or false or clipping region or no. I finally discovered that I can get at those menus by using Alt+f or Alt+<down arrow> to drop the first menu down. The window bar may be hidden but it is still there and accessible. Note that this doesn’t work until iGuidance has been running for about 2 mins. I am not sure why but it won’t respond to keystrokes until that time. To further complicate matters my in-car keyboard (the mini usb keyboard from the store here) doesn’t have alt keys so I had to setup a custom keystroke macro on my shuttleXpress. I did discover after all this that the two things I wanted most from the menus are available in other ways. I wanted demo mode (which is available on the destination menu after a route is active and I wanted trip calculator which will popup if you press T.
Sound:
Finally I wanted the sound to lower to around 25% when IG was giving voice directions. The setting in the RRConfig didn’t make any difference for me and just caused confusion.
I spent hrs and hrs on this. Here is what worked.
Put this in your RR ExecTBL.ini
"IGPAUSE","!PRESET;IG3;WINAMP||SETVOL;WINAMP;5 0"
"IGRESUME","PRESET;IG3;WINAMP"
The 50 at the end of that line will vary from person to person. Try different values between 0 and 200.
Set pauseonvoice=true [in RR.ini]
It’s a bit of a misnomer. Set this way pauseonvoice=true will not pause but will lower the volume.
The last thing that is needed is for the volume level in IG to be somewhat different than your winamp volume. My winamp volume is always at 100% so I set IG to be one notch below 100%. Then it started working.
Oh, btw, when I couldn’t get the sound working I read on here that the latest version of winamp that works flawlessly with RR was 5.13. I had 5.2 installed so I uninstalled it and installed 5.13. I have no idea if that made any difference as I didn’t discover the ExecTBL.ini settings until after that.