Transfer Caller Announcement to BT headset

[StevenLawyer]

Lennyish and Yuma6700--You guys are great. Thanks for all the replies and help. I haven't loaded Yuma's script yet but will do so within the next few minutes and let you know how it works. Just wanted express my gratitude in the meanwhile.

Also, where can I self teach to do these types of scripts? Any good learning resources?

[Perasite]

Treocentral's forum has a Mortscript developer's forum that is great. I go by perasite over there. The way I learned was by taking a look at some of the stuff other's posted and then trying to do the stuff I wanted using their's as a guide. Also, that link to the Mortscript site in my last post has the manual which tells you how to do a LOT. (I used it on this script to figure out how to make the announcement message disappear. Couldn't remember...)

[Perasite]

Oh, and take a look at the software posted in my sig line. All of that uses MortScript, so there's a lot of info that can be learned by looking at that code.

[Perasite]

Thanks, I'm at work, so didn't have access to a .cab maker. I never use option 2, so that's a good add. What were your Dword values as compared to the ones I had? I tested it on mine and was getting the change I expected. Just curious.

[Perasite]

OK, I see the change, actually we are both right and both wrong. See I don't have the box checked to use "Only during free time" so the if/then statements on this update don't make any changes to mine. On mine, it would make no changes to yours. I'm gonna write it up with all the proper flags and attach. Could you put it into the cab once I do?

[Perasite]

OK, this is the .mscr file only. It has all the possible flags. If you use the second option (Use BT when available) then it will switch to Speaker and from there alternate to BT only and back and forth like that. This accounts for having the "Only during free time" checkbox, and will maintain that setting as you toggle back and forth. If Lennysh doesn't get it packaged up, you can just copy this over his in \Windows.

[StevenLawyer]

Originally Posted by lennysh

Attached is 6700Yuma's Mortscript in CAB format inside the zip.

Lennysh and 6700Yuma:

Thanks for all the work. I installed Yuma's original version prior to these updated ones. Here's what I discovered. The app switches the settings in VC fine, but the change doesn't actually take effect unless you go to the VC settings screen. I presume the app by Yuma changes the registry values but apparently VC doesn't read them and actually change its operation unless you go to the VC settings page. As I said, I haven't tried the updated versions you posted, but I assume the problem occurs with those too? Obviously, the purpose of the app is defeated if, after running it, one has to still go to VC settings. I assume the problem could be fixed by having the app change the registry values and then merely open and then close VC settings. I found that you don't even need to go to the notifications page in VC settings to get the change to be effective. You need merely go to the initial VC settings page and then can immediately exit to have the changes be effective. Anyway to change the app to do this?

I truly appreciate the work you've both done!

[lennysh]

Attached is 6700Yuma's Mortscript in CAB format inside the zip. I edited it because on my 6700, the Dword Values were different than mine. It now also changes option 2 if you happen to have it set on 2, to either 1 or 3. Then it will only alternate between 1 and 3. So to set to option 2, you would have to do manually.

6700Yuma gets full credit, as you will see in the filename, and cab name, and app name. Hope you don't mind 6700Yuma. I just mainly cabbed it up... Also, you no longer have to run the exe first. The cab does what the exe does automatically. This cab will put the lnk to the script in your programs directory, so you can assign to any hard button on the device, or add to your start menu.

Let me know if this helps...

EDIT: This is the updated cab install. I didn't even think about that checkbox making a difference. Thanks 6700Yuma for pointing that out. I was wondering where you got your values.. lol.. But I was at work, and in a rush to get this out before I left work, that I didn't try to figure it out.

EDIT #2: It now opens the voice command control panel applet after it applies the setting, and then closes it.

[StevenLawyer]

Yuma6700 and Lennysh: You guys are cool. App in latest permutation works great. I just sent you each $25.00 via Paypal--I figured I'd split the $50 I said this was worth to me between the two of you. Thanks agains so much. I know you didn't do this for money and probably spent more time than what I gave, but please accept it as my thanks. Without folks like the two of you, the rest of us would be lost.

[StevenLawyer]

Originally Posted by lennysh

Attached is 6700Yuma's Mortscript in CAB format inside the zip.

Lennysh and Yuma6700:

Well, I discovered one other bug. If you run this app via voice command when the 6700 is locked, it doesn't work. It gets to the point of the open settings screen for voice command, but doesn't exit the settings screen, which is apparently necessary in order for the settings to take effect. So the change doesn't occur unless you unlock the PPC and exit the settings screen.

I normally keep my 6700 locked while on my side, because otherwise buttons tend to get bumped. I then do most of my usage through bluetooth VC (such as dialing, etc.) So, for my usage, it would be ideal if your app would work if run while the unit is locked. That way, when I'm going to be wearing by BT headset, I could just run the app via VC and then just before I take it off, I could run the app again without unlocking it. I have renamed the lnk to "Transfer Ring" and can just hit my BT switch and say "Start Transfer Ring". The app runs fine when I do this, but only if the 6700 is unlocked. If it's locked, then I run into the problem I've just described. Anyway to get the app to successfully exit the settings screen if the app is run while the unit is locked?