leelg

Thanks! That is excatly what I was looking for. I guess it was just to late in the evening :oops: . I scanned the SDK panels doc but didn't think about checking the header file. Sorry to take up your time and THANKS! Lee :D :D BTW, it never ceases to amaze me the things that can be done with FSUIPC.

Pete, I assume you added this to FSUIPC since it is possible to map buttons to turn panels on/off. This is great but I have a related question. Do you know a way to determine the panel ident for panels with string or enumerated names? For example, what is the numeric ident for the "Collective_panel". My aircraft has several named panels and I need to make sure they are off which seems to be only possible by supplying a numeric panel id. I am hoping if you don't know the answer, someone else will. Thanks! Lee

No problem Pete. There are other ways to solve the problem. I currently use a joystick connected to the client to change views and it works fine. I can also use Go-Flight hardware as well. I was just trying to make it work with my yoke buttons but that will have to wait. It's not big deal. I looked at the Key2Lan but don't think it will do what I want. I will request an additional feature to send keypresses in addition to mouse clicks. You are correct that it is the preferred solution. Thanks! Lee

One other piece of data. I ran a WideFS client on my server PC with FS9 running and the exact same thing happens. It is not unique to my client but seems to be a problem with a WideFS client and FS9 running on the same computer. Lee

Pete, I tried what you suggested and the behavior was exactly the same. I did a bit more investigating and it would appear there is a bad interaction between the WideClient and FS9 even with a different ClassInstance for the client. If I keep FS9 in a window and have WideFS as a window next to it, it seems the WideFS client does not get any (or very few) CPU cycles. If FS9 has focus, WideFS cannot seem to take the focus away. The WideFS window border is in non-focus mode and clicking on WideFS will not give it focus. Only minimizing or closing FS9 gives the WideFS client focus. The WideFS client program appears locked up. Other programs do not have any problem taking focus from FS9. I do not have WideServer on the client and I removed FSUIPC as a test but it did not make any difference. So, it seems the keypress events are being received and processed but because WideFS is getting so few CPU cycles, the keypresses take a long time to get to FS9. That is the best description I can provide. I turned on debug logging but did not see anything of interest. It doesn't seem like WideFS is getting errors, it is just very slow. Any ideas? thx, Lee

Thanks for the quick reply Pete! I will play with it some more when I get the final release. Maybe there is something a bit different in the pre-released version you sent me. Lee

I guess I will have to wait until the latest release is posted to test. Lee

Pete, I think there still may be something odd regarding the WideFS keystroke generation. I am attempting to control a copy of FS9 on a WideView attached client PC with a joystick button on the server with the primary FS9. What I want to do is change the FS9 view on the WideView client. According to the WideFS documentation, this should be possible by changing the classinstance value for the WideClient. After changing the classInstance value, I was able to run WideClient on the WideView client PC without a problem. I set up the keysends to generate keystrokes to change the view. I tested the keystrokes with wordpad and WideFS properly sent the keystrokes to WordPad on the client PC. I started up the FS9 client and verified the keystrokes worked when entered from the keyboard on the client. When I sent the keystrokes from the server, WideFS does not properly control FS9 on the client. The keys seem to be ignored (no view change). I tried to save a flight so I could enter keys into a text field for a test, the keystrokes would display but the spacing would not advance (using SendInput). The keys would over wright each other. Without SendInput turned on, I could never get a key to display with FS9. When I programmed a switch with FSUIPC to control the server FS9 view via the same keycode, it works just fine. Have you ever tried this? Does FS9 use some odd keyboard processing like Teamspeak? Could there be some bad interraction between WideFS and FS9 on the client? It seems there still may be a variation between the FSUIPC keyboard processing and WideFS. Any ideas? I am going to download and try the latest FSUIPC and WideFS and see what happens. I will report back. thx, Lee

Pete, It works!! Please see my email. Lee

Sorry Pete, no luck. I tried 6.417 as you requested but it did not make a difference. Just so you know what I did. 1. I tested WideFS 6.417 with WordPad. When I run WordPad from WideFS and send the keys, the correct key is displayed (K). 2. I changed the setup but used Teamspeak instead of Wordpad. I pressed the "K" on the keyboard and the transmit light works. When I pressed the joystick button, nothing happens. If I change focus to WideFS, the focus goes back to Teamspeak when I press the button. Any other clues? Lee

Pete, Negative on all fronts. I tried your suggestions and it made no difference. Interestingly, when Postkeys=yes, I was not able to get a keypress to any program. What does work is Teamspeak running on the SAME PC as FS. When a button is programmed to key Teamspeak on the SAME PC as FS, it works fine. When attempting to run TS on a remote PC with WideFS, it does not work. I believe your last idea was probably correct. There is some difference in your use of SendInput with FSUIPC and WideFS. Thanks! Lee

Pete, I have been trying to get Teamspeak to work and discovered the problem you describe. My question is why does it work when running on the same PC as FSUIPC and not with wideFS? What is different on how you generate keypresses? thx, lee