I think that you don't need to minimize any application, but only execute Show ("NAVI") will bring back Primo and hide other running application behind, which is the intent.

In my end, I started modding my v3.3 MOD and have implemented the auto-timer to launch Primo, if this option was selected from the Custom Settings menu.

I have carver's hack for the nag message so whenever I start my AVIC, it automatically gets into the map screen, and the 15-second visual countdown timer starts. You will be able to press the timer anytime to stop it, and change the setting if wish. A longclick will launch Primo without waiting for the end of the 15s countdown.

My only problem now is that once I launch MainMenu from Primo, I have no easy mean to go back to Primo. Your hack with the AEKMap.exe has only one thing working: Menu button. The reste is not working for me.

But because I have carver's hack so I have an option: the only way that I've found is to go into the System Settings, open Explorer or Show Taskbar, then click on the "NAVI" label on the bottom to bring back Primo; or use scripts or shortcuts from the "Start Menu" when launching Primo from my Mod v3.3. Works fine but not user-friendly.

Unzip the attached file in your iGo folder and overwrite all your existing modified .UI files. Go to Custom Settings to select Primo as the "Start Nav App" (still ongoing and it has to be renamed later though).

ui_pioneer.zip

http://www.youtube.com/watch?v=lGIYGvDVBVM&feature=feedlik

 

edit: this is in italian!

The menu looks identical to the Russian mod. I'll bet they modded it to Italian. I tried the Russian mod yesterday and it would be hands down the best mod... if I was Russian. So far as I know no one converted it to English yet. Any idea where to find the mod in the video?

I think that you don't need to minimize any application, but only execute Show ("NAVI") will bring back Primo and hide other running application behind, which is the intent.

 

In my end, I started modding my v3.3 MOD and have implemented the auto-timer to launch Primo, if this option was selected from the Custom Settings menu.

 

I have carver's hack for the nag message so whenever I start my AVIC, it automatically gets into the map screen, and the 15-second visual countdown timer starts. You will be able to press the timer anytime to stop it, and change the setting if wish. A longclick will launch Primo without waiting for the end of the 15s countdown.

 

My only problem now is that once I launch MainMenu from Primo, I have no easy mean to go back to Primo. Your hack with the AEKMap.exe has only one thing working: Menu button. The reste is not working for me.

 

But because I have carver's hack so I have an option: the only way that I've found is to go into the System Settings, open Explorer or Show Taskbar, then click on the "NAVI" label on the bottom to bring back Primo; or use scripts or shortcuts from the "Start Menu" when launching Primo from my Mod v3.3. Works fine but not user-friendly.

 

Unzip the attached file in your iGo folder and overwrite all your existing modified .UI files. Go to Custom Settings to select Primo as the "Start Nav App" (still ongoing and it has to be renamed later though).

You mean the Map button doesn't bring you back to Primo from the Main Menu? It should, it does on mine. The AEKmap will launch the "showmainmenu" mortscript file on a menu press and "showprimo" on a map press. For some reason it doesn't maximize Primo when in AV, just from the top menu (AV superseds all?). Oddly, it does go to Primo from the AV if the run explorer command is present in the CwGoPrimo.mscr. I just hate seeing explorer briefly between screen change. Make sure you are at the Top Menu screen then press Map, it will work!

Edit: Autolaunch works great, thank you Chuck!

Ryar,

The mod in italian: http://depositfiles.com/es/files/4vo2xsswu

The link to italiam forum: http://pioneernavgate.blogfree.net/?t=3453274

Well, since the hard buttons are buggy we will move on to plan B until they are fixed. Copy the file below onto your unit and an icon will appear in the top right of the Top Menu which will bring you back to Primo. AEKMap is disabled, for now.

See post #85 for new files, if this was installed after Chuck's autolaunch package it will generate errors. It so, reinstall his ui_pioneer and it will work.

 

You mean the Map button doesn't bring you back to Primo from the Main Menu? It should, it does on mine. The AEKmap will launch the "showmainmenu" mortscript file on a menu press and "showprimo" on a map press. For some reason it doesn't maximize Primo when in AV, just from the top menu (AV superseds all?). Oddly, it does go to Primo from the AV if the run explorer command is present in the CwGoPrimo.mscr. I just hate seeing explorer briefly between screen change. Make sure you are at the Top Menu screen then press Map, it will work!

 

Edit: Autolaunch works great, thank you Chuck!

Good! I forgot to include the CW_icon_primo.bmp but I guessed you have it copied by yourself ...

This will be my upcoming small update v3.4 and it already includes a couple of improvements, that I forgot the details since I never thought before that I am going to release my mod again ... I will compare to v3.3 to see what have been changed or improved, when I have sometime. Once your works is in an acceptable state, let me know and I will release it. Hopefully this time will be my final mark (I just cannot keep good thing for myself) .

However, I don't intend to support Primo even though there is a link to it. I will forward users to your thread for further support.

Well, since the hard buttons are buggy we will move on to plan B until they are fixed. Copy the file below onto your unit and an icon will appear in the top right of the Top Menu which will bring you back to Primo. AEKMap is disabled, for now.

 

ryar, I think that "\My Flash Disk\APL2\Primo\extension\Button\button.exe" was not included in your planB.zip .

 

ryar, I think that "\My Flash Disk\APL2\Primo\extension\Button\button.exe" was not included in your planB.zip .

Oops, it was already on my unit so it worked when I tested it. Fixed!

Now I am getting a FFGUI error when turning on the unit with autolaunch Primo selected. It reads:

FFUIERROR: Unknown object identifier.

Identifier=(sc_CwPrimoAutoLaunch)

Script "st_navigatemap_init" command 18

Weird, it worked fine the 1st time.

 

Oops, it was already on my unit so it worked when I tested it. Fixed!

 

Now I am getting a FFGUI error when turning on the unit with autolaunch Primo selected. It reads:

FFUIERROR: Unknown object identifier.

Identifier=(sc_CwPrimoAutoLaunch)

Script "st_navigatemap_init" command 18

 

Weird, it worked fine the 1st time.

ryar, you have to get rid of your own modified chuck88.ui and chuck88_800_480.ui, but only use mines. You probably recopied those two files over my set of files.

 

ryar, you have to get rid of your own modified chuck88.ui and chuck88_800_480.ui, but only use mines. You probably recopied those two files over my set of files.

Indeed I did, they were part of PlanB. Reinstalled your package and it is working. So to be clear, Chuck's ui_pioneer should be reinstalled for those who put the old planB on after. The new planB with no ui_pioneer files is below.

Removed

Well, one last update then gonna update the main download in post #1 after I test everything on a clean install of My Flash Disk. Hard button control is now optional, you can try them out by downloading the file below and launching the "HardKeyTest" through external programs (in the quick menu). Make sure to rescan programs so it shows up. It seems Primo and Pioneer don't play nice together and the buttons can only used by one or the other. If you launch "HardKeyTest" you will lose default functionality of the buttons (main volume control, next song, ect), but gain use of the buttons inside Primo. This means you can zoom/pan, the volume control inside Primo is controlled by the dial, the menu button brings you to the top menu, and the map button brings you back to Primo from the top menu. Do not use these buttons while in AV (Av Source, ect) as the AV screen stays on top off all other screens and you will experience strange behavior. Note the default use of the hard keys is restored by rebooting the unit. The soft key on the main menu is also included, which is an icon in the top right of the Top Menu screen which will bring you back to Primo.

Also changed close ("iGo8") to back to kill ("ezrider"), close didn't free up all the memory that kill does and was getting out of memory errors.

planBandButtons.rar

edit: Great, it tests OK and everything is working. Chuck, what, if anything, should I include in the iGo\extension and ui folders besides CwGoPrimo.mscr?

edit2: Make sure you have in your Primo sys.txt:

[Keybind]

xa6 = "ZOOMIN" ;Up

xa8 = "ZoomOut" ;Down

xC4 = "MINIMIZE" ;Menu

xaf = "VOLUMEUP" ;Dial right

xae = "VOLUMEDOWN" ;Dial left

xD5 = "ROTATELEFT" ;Left

xa7 = "ROTATERIGHT" ;Right

xC3 = "MAINMENU" ;Map

x8D = "ANNOUNCE" ;Middle button

ryar, thank you for your efforts by digging so far; I think your solution is viable enough for almost everybody.

Good find on the Close() vs Kill() command, I just realized the same.

The CwGoPrimo.mscr is the only file to put inside iGo\Extension, but please add Kill("EzRider.exe") in addition to the Kill("EzRider") command, because if you chose to launch again iGo8, the process name will be EzRider.exe instead of EzRider (initial process name).

I will probably tweak further my scripts to facilitate my wife's life, because she still doesn't know how to use Primo and prefers iGo8, so I will add a stop-popup-message to prompt if Primo is selected, addition to the Autolaunching feature.

---------------------------

Are you going to call the HardKeyTest.exe in the CwGoPrimo.mscr? Perhaps you should rename the HardKeyTest to something else more relevant.

Further to updating the first post (huge), can you post the trimmed version of your latest here in the post, without Primo v1.2?

Thanks.

Gentlemen, please help with GPS. Still it lasts, if it gets going and return to Priimo - still looking for GPS! What am I doing wrong??

Thanks.

1) In the iGo8 SYS.txt, select the device matching your AVIC.

2) Use the proper script to Kill("EzRider") within CwGoPrimo.mscr. Please wait for ryar to release the "Official" one soon.

Gentlemen, please help with GPS. Still it lasts, if it gets going and return to Priimo - still looking for GPS! What am I doing wrong??

 

Thanks.

Do you get a GPS fix in Chuck's mod? Is the screenshot you posted in post #13 the same problem you are having now?

Yes, it's still the same ...

Yes, it's still the same ...

Maybe try delete \Primo\save\route.dat and restart? Did you delete and reinstall the Primo folder at any point (try this second)?

edit: I see there is a command in the sys.txt which reads:

[utility]

calibratefix=0 ; ; If gps signal don't lost write - "0"; if lost write "1"

Maybe try change it to 1 if you still can't get it to work.

ryar, thank you for your efforts by digging so far; I think your solution is viable enough for almost everybody.

 

Good find on the Close() vs Kill() command, I just realized the same.

 

The CwGoPrimo.mscr is the only file to put inside iGo\Extension, but please add Kill("EzRider.exe") in addition to the Kill("EzRider") command, because if you chose to launch again iGo8, the process name will be EzRider.exe instead of EzRider (initial process name).

 

I will probably tweak further my scripts to facilitate my wife's life, because she still doesn't know how to use Primo and prefers iGo8, so I will add a stop-popup-message to prompt if Primo is selected, addition to the Autolaunching feature.

 

 

---------------------------

 

Are you going to call the HardKeyTest.exe in the CwGoPrimo.mscr? Perhaps you should rename the HardKeyTest to something else more relevant.

 

Further to updating the first post (huge), can you post the trimmed version of your latest here in the post, without Primo v1.2?

 

Thanks.

Well here it is, hopefully the last update. Can you try it out and let me know how everything works? If so then I will attach it to post #1 (and clean up the post). What is included:

- Button included in the Top Menu Screen at the top right which brings you back to Primo.

- HardKeyTest, which can be run from External Programs (in Primo's Quick Menu). It takes hard key control from Pioneer/main menu and gives them to Primo. It is labeled "test" because you can try it and decide where you want the keys mapped to Pioneer (default) or Primo. For GPS use only, I prefer it mapped to Primo but for music use, ect it would probably be better to leave keys as is to control music volume, song, radio station, ect. After running HardKeyTest reboot to regain default use of buttons. The name can be changed in external programs for those who don't like it It would be easy enough to throw in a command to launch the HardKeyTest in the CwGoPrimo.mscr; I have a feeling the majority would like to use the buttons as is. There is no need to use this file when launching from testmode, all buttons work using this method. Note the hard keys DO NOT work in Primo 1.1, even with the same keybind commands in the sys.txt file.

- CwGoPrimo.mscr includes both kill ezrider () and kill ezrider.exe ()

- sys.txt cleaned up and added all keybind commands with AVIC button labels if anyone wants to play with mappings/button functions. Most iGo8 keybind functions don't work, unfortunately.

That's it! Well that's as functional as I could get it with our units. I also deleted all the skins but GJ 10.0 for the main download which shrunk the file by nearly 50 MB.

Deleted, updated

ryar, don't know what was wrong:

1) I would say 40% of the time when HardKeyTest is launching, my AVIC (X710BT) reboots.

2) Numerous times, showprimo.exe said there is no enough memory while TaskManager reported 130 MB available.

Can you confirm whether the following command will launch Primo IF not yet done, and will maximize/restore Primo IF already launched?

Run ("\My Flash Disk\APL2\Primo\Primo.exe" )

ryar, don't know what was wrong:

 

1) I would say 40% of the time when HardKeyTest is launching, my AVIC (X710BT) reboots.

2) Numerous times, showprimo.exe said there is no enough memory while TaskManager reported 130 MB available.

 

Can you confirm whether the following command will launch Primo IF not yet done, and will maximize/restore Primo IF already launched?

 

Run ("\My Flash Disk\APL2\Primo\Primo.exe" )

Darn, it seems we are experiencing different behavior on different units. Weird with the reboots, I never even had that happen once. My hard keys are working flawlessly!

I can confirm that Run ("\My Flash Disk\APL2\Primo\Primo.exe" ) will launch if Primo if not yet done , and maximize if it is. That command is in several places (CwGoPrimko.mscr, showprimo.mscr, HardKeyTest, button.exe config). I cannot confirm that it is a better methed then show("navi") for maximizing Primo. After reading your post regarding reboots and memory errors, I think the show command is safer.

Can you tell me if the button is working in the Top Menu which brings you back to Primo? If so I will remove the HardKeyTest if you still don't have any luck with the new show commands.

The file below has all Run primo commands changed to show navi. It hopefully will eliminate memory issues, can you please try it ?

Deleted, updated

 

Can you tell me if the button is working in the Top Menu which brings you back to Primo? If so I will remove the HardKeyTest if you still don't have any luck with the new show commands.

 

I still hang on to the HardKeyTest.exe and will try again. Rather than calling manually, I embed its contents to the CwGoPrimo.mscr (with 3 seconds sleeping). One thing for sure, when the command was executed without error, the MAP key does bring the screen back to Primo, MENU key show top level menu, ZOOMIN and ZOOMOUT work too, which is the intents.

kill ("ezrider")
kill ("ezrider.exe")
Run ("\My Flash Disk\APL2\Primo\extension\AEKMap\AEKMapScan.exe" )
sleep 3000
kill ("AEKMapScan.exe")
Run ("\My Flash Disk\APL2\Primo\extension\AEKMap\AEKMap.exe" )
Run ("\My Flash Disk\APL2\Primo\extension\Button\button.exe")
Run ("\My Flash Disk\APL2\Primo\Primo.exe" )

I will post back results.

ryar, WinCE "Fatal application error" for AEKMapScan.exe, but after the kill() command, the message disappears by itself, and guess what, all intented hard keys are still working ... weird! Looks like 3000 ms is enough before the kill() command.

Why do you put 5 seconds?

However, the "Primo crashing on exit" has returned, even after launching Primo directly from Explorer, so the only change that caused the crash should be in SYS.txt (since my post on the 17th of September).

Any idea ryar?

ryar, WinCE "Fatal application error" for AEKMapScan.exe, but after the kill() command, the message disappears by itself, and guess what, all intented hard keys are still working ... weird! Looks like 3000 ms is enough before the kill() command.

 

Why do you put 5 seconds?

 

However, the "Primo crashing on exit" has returned, even after launching Primo directly from Explorer, so the only change that caused the crash should be in SYS.txt (since my post on the 17th of September).

 

Any idea ryar?

I put 5 seconds just to be safe, if 3 works then I will change it.

By crashing on exit do you mean the unit rebooting? Mine always did. The only changes to the sys.txt were that I added were the Keybind commands and

[power]

powermgm_state="1"

skip_suspend_process_all="1"

which may be the culprit. I don't think that part is necessary.

The hard keys still work after the program crashes because only it's launch is required (to allow Primo and AEKMap to bind the keys), and leaving it running would server no purpose. I will test a close command on it instead of killing it.

Thanks for testing! I will delete the unnecessary additions to sys.txt and change the delay in the HardKeyTest to 3 seconds.

ryar, I think the kill() command on HardKey is OK, better than close(). The WinCE fatal msg is happened before the kill() command, so no need to change it.

Do you think that we can minimize() the Mortscript v4.2 application ... it is a bit annoying during Primo startup.

ryar, I think the kill() command on HardKey is OK, better than close(). The WinCE fatal msg is happened before the kill() command, so no need to change it.

 

Do you think that we can minimize() the Mortscript v4.2 application ... it is a bit annoying during Primo startup.

OK so long as it works the hardkeytest works I won't worry about changing it.

The Mortscript v4.2 now auto-closes shortly after opening (via a sendOK command).

This should be it (I hope). Can you think of anything else?

planBandButtons09.22.11.rar