Once CA3 has turned it on / off, Comm Manager can't control it. I am investigating...
Jump to content
Create a script file with the following contents ( I use \My Documents\My Scripts\autocameraware.mscr):-RunCheck = 0Application = "\Storage Card\Program Files\CamerAware 3\CamerAware3.exe"WindowName = "CamerAware"While (1) HandsFreeState = RegRead("HKLM", "System\State\Hardware", "Handsfree") If (HandsFreeState = 1 && RunCheck = 0) ToggleDisplay(1) SetVolume 255 Run (Application) RunCheck = 1 EndIf If (HandsFreeState = 0 && RunCheck = 1) If (wndExists (WindowName)) Close(WindowName) EndIf SetVolume 100 RunCheck = 0 EndIf Sleep (5000)EndWhile
Then create a shortcut to that file in \Windows\Startup.
I could actually monitor state changes (such as leaving handsfree) in CA itself and exit automagically...
Cheers for that.
Have you found a clean way to shutdown CA when you leave the car - using Mortscript?
This script already does that.
Might be worth you waiting for Paul to incorporate this in his code.
Both those functions work as intended on mine...? Anyone?
The updating of the camera database doesn't appear to work. Just updated v2 fine.
I can't be sure but think i had this trouble with the last v3 release.
Also, selecting the "about" option causes ca to crash.
Select a different option (e.g. 'Navizon Stats') to clear that caching and you'll be sorted.
Downloaded & installed the latest build.
Odometer and Navizon Stats ticks still appears when it's being run for the first time. But I am assuming it's cached from previous build. (registry)
Will give it a proper test on the way home.
Edited by pjam001, 16 January 2008 - 03:49 PM.
0 members, 0 guests, 0 anonymous users