Originally posted by Bob Church@May 3 2005, 07:20 AM
Hi Josh,
>> Thanks for getting back to me . <<
You're quite welcome!
>> Fisrtly as to do the windows toggle with the same command. is yes
mode2 Nav/com is (@)
mode3 GPS is (#) <<
Okay. I thought that was the case but I couldn't recall offhand how they worked.
>> Howerver in the next paragraph to the CURRENTMODE constant is the FTRSTKMODE which mentions similar values depnding on the Led last on. If you could guide me down this road would be great, as there are'nt any examples in the CMS guide for it. <<
The main difference is that FTRSTKMODE tells you which mode the FighterStick itself is in, basically just which of the LEDs is on. CURRENTMODE tells you which mode the Control Manager is in. If the FighterStick is designated as the Mode Control on the Program Settings page like you're talking about doing, then the two are the same. If you were using a Pro Throttle or CMS programming to control the Mode, CURRENTMODE and FTRSTKMODE wouldn't necessarily match. Also, you can set CURRENTMODE with a CMS script and the Control Manager will change modes, but FTRSTKMODE and PROTHRMODE are Read-Only. Anyway, since you're using the FighterStick normally, it doesn't really matter which one you use.
The problem with the toggle is that you need to hit it twice, once when you enter the mode and then once again when you leave, and there is the chance that it will get out of sync, you might hit the key on the keyboard by mistake and open the Window in another mode. If it happens just hit the key again to get it back to where it should be.
Anyway, basically what you need to do is to first add the CMS Controls to your map. Once you've done that, you can open the CMS editor and write a small script:
script
cms.b1 = [ CURRENTMODE == MODE2 ];
cms.b2 = [ CURRENTMODE == MODE3 ];
endScript
Save the script and go close the editor. Next, select the CMS Controls tab and select Button 1. Make sure you've got the "Mode 1" tab selected. Uncheck the "DX Mode" box, then in the "Normal Action" section set the "Press" box to send:
@ NULL
and set the "Release" box to send:
@
Next do the same for Button 2 but set the "Press" box ot send
# NULL
and the "Release" just to send:
#
That will cause it to send one "@" or "#" when it enters the Mode to open the window, then another "@" or "#" when it leaves the mode to close the Window. You only need to program it on the Mode 1 Tab. When the other tabs are left blank, they'll use the Mode 1 programming, too.
That's about all there is to it. You might have to cycle through the modes once at the beginning of a flight to get them synchronized, but that's about the only problem I can see.
Best regards,
- Bob
The StickWorks
http://www.stickworks.com
<div align="right">12399
[/quote]
Hello again Bob,
I have done as U instrucred to a T, no problem there,and checked
it twice. However in the sim I get no responce.
To clear a few things up through, do I have to select CMS mode
control in the PROGRAM TAB or leave it to the stick? And how come there is no
reference made to a stick button in the script? EG. js1.b3
Could U also explain the use of the square brakets in the script and parenthicis in general. I have managed to asign a cms.bx to a js1.bx for no good use mind U, but dont asume I know anything. If you do make reference to the users guide I have probebly read it and be able to recall it.
Cheers and thanks again
Regards Josh