Ken_Salter

Yes, it can be moved. I too would like to divert the details elsewhere, but short of that I was thinking that if I could detect (or open by sending a ~) the window, then I could read the contents and write a parser to figure out what is going on. Then when the user reacts I can interpret and send the correct keystroke (number) to MSFS. Further problems exist however, which makes me wonder if my project is worthwhile. For example, is there any way to mute the pilot replying to ATC? Also, would there be a way to detect if ATC or another pilot is talking so I don't send a keystroke only to have to send it again? Thanks, Ken Salter AVSIM.com

Well, that's a shame. Would you (or anyone else) happen to know if the window that is displayed for ATC is a Win32 window that I could get a handle to? I haven't run Spy++ yet on MSFS. If I could get a handle then I should be able to read the contents. I seriously doubt that this is a window with a handle, however. Thanks, Ken Salter AVSIM.com

Pete et al: I tried to search for this but couldn't find anything, so please forgive if this has been answered before. I was wondering if it is possible to use FSUIPC to "read" what the current options in the ATC window are. I'm not looking to control ATC per se, but to be able to know what ATC is expecting from the user. If this is not possible then I would have to maintain a state engine in my software and intercept the keystrokes from the user (further I would have to figure out all possible states for the ATC windows). Thanks for any help you can give! Regards, Ken Salter AVSIM.com