ark1320

Ah, I have learned something! Thanks Pete and John for the clarification. As you can tell, my programming experience has been limited. I expect you could also use a return if you need to exit the function early before the end, e.g., in the middle of the function body based on some data variable. Best, Al

What I'm asking about regarding the return instruction is I normally think of a function definition as having the form: function name( params ) body of the function return -- return to where function was called from end I was surprised to see that the mytimer() and keyPressed() functions did not have a return instruction to transfer code execution back to the calling location. BTW, do you have any idea at this point about when FSUIPC7 will be updated again? Thanks for your time with all this, Al

That fixed the issue with resizing/moving the window -- thanks. Just to clarify, so if an event function call like event.key() is called as part of a larger function, does that event remain active even after the program returns from the larger function? BTW, I noticed the mytimer() and keyPressed() functions did not end with a Return instruction -- does that have something to do with the nature of the event .cancel() function calls contained in the mytimer() and keyPressed() functions? Thanks, Al

John, I'm trying to understand how the askTest script works and thinking about how to incorporate the askTest code in a larger program. At first I was just going to make the askTest code into a 'large' function that could be called as needed, but now I'm wondering if that will work with the event type function calls the script contains. Can event calls be internal to a called function, or do they essentially have to be part of the main program since they just sit and wait to be triggered? It seems from the askTest code that if you have 10 event.key() functions then you need 10 event.cancel() functions -- apparently one event.cancel () function will not call all the event.key() functions? BTW, I see the line event.cancel("mytimer2") but do not see any function named mytimer2. I assume the 2 in the function name is a typo. Thanks again for the script, Al

Hi John, Thanks very much for the script. I've been trying it a bit and it seems to work (although just a few times nothing happened when I pressed the key I have assigned to run it -- maybe some kind of timing glitch). What didn't work is changing the numbers in the code line that defines the display window local w = wnd.open("Asking for inout: test", WND_FIXED, 500,200,500,60) Nothing I did made any difference for some reason. I have tried restating both FSUIPC7 and the sim after changing these numbers but don't see any change when the script is run. I will keep experimenting with the script a bit later today. Al

Agree! And I really appreciate your and John's support efforts. Al

I have to wonder if Asobo realizes just how messed up their text functions are, at least when used through SimConnect. Even when a Lua single line text display shows up correctly, if often displays multiple times for no apparent reason. If you could come up with a work around, that would certainly be VERY helpful. Thanks, Al

Hi John, Your update to FSUIPC7 seems to work as expected. Thanks very much! Al

I know the Numpad number keys now work correctly, but don't see anything I recognize in the SDK about the keys I mentioned above. Thanks for the response, Al

The key codes that FSUIPC7 'sees' through SimConnect for the Page Dn, Page Up, End, Home and Insert keys seem to be incorrect. For example, the log file shows FSUIPC7 sees a key code of 99 for the Page Dn key, but it should be 34. Key code 99 is the Num3 key code. I discovered this because the keys listed above have been triggering a Lua script even though the FSUIPC7 key assignment window, and the FSUIPC7.ini file, show these keys are not assigned. Al

From what I can tell, the ipc.ask() lua function does not currently work in MSFS. Is there another way with MSFS to get a multi-digit numerical variable value entered by the user into a Lua script at script run time? I'm trying to write a script that asks the user to input a number value of their choice between 1 and 999. Best wishes for the holidays! Thanks, Al

Ron, If this is a default aircraft and you switch on the strobes just using the default Asobo control, I assume a mouse click, does the battery still get turned off? If not, I would guess you have a FSUIPC setup conflict somewhere. Al

Yes, I saw they were not listed. I can certainly get by without them. Al

In case you missed my late edit above, two keys that don't work are the stand alone <, and >. keys. Al

BTW, although the current SDK shows the Shift, Ctrl, and Alt keys as 'fail', they all seem to work as part of a key combination, which is good news. Two keys that don't work are the stand alone < and > keys. Just FYI. Really appreciate the super support! Al

YES-- arrow keys work!! Thank you Thomas and John! Al

Agree, makes good sense. Al

OK, I see, thanks for the explanation. Seems strange and unfortunate to me that they would not make all the keys commonly found on a keyboard available via SimConnect. They certainly make use of the arrow keys in the MSFS default key bindings, so why they would not think these keys would also be useful to third party applications via SimConnect is baffling. Making it clear certain common keys won't work with FSUIPC7 will likely help prevent users from spending a lot of time trying to figure out why something doesn't work. And hopefully save you time by eliminating the need to respond to posts like this one! 🙂 Maybe some kind of popup " Key not available" message when a user tries to assign a non-useable key would be good. Thanks for the help, Al

BTW John, this issue with the arrow keys seems to be the same problem as we had with the Numpad number keys in that arrow key (or the arrow keys in combination with Shift, etc) control assignments work IF FSUIPC7 has focus. Al

John, In the FSUIPC6 Key presses drop down controls list I have the stand alone Left and Right arrow keys assigned to Heading Bug Dec and Heading Bug Inc, and the stand alone Up and Down arrow keys assigned to Ap Alt Var Inc and Ap Alt Var Dec, and all works fine. That is what I wanted to do in FSUIPC7, but no luck. If when convenient you could let Asobo know maybe they will eventually fix this. I would expect the arrow keys are used by many with FSUIPC. Thanks for the feedback, Al

John, As best as I can tell, the Up, Down, Left and Right arrow keys still do not work correctly in FSUIPC7. I assume this is a continuing Simconnect problem -- can you confirm this? As a test, I wrote a very simple Lua script that does nothing but display a few words on the screen, and assigned the Up arrow key to activate the script -- doesn't work. However, if I assign a non-arrow key, it works. Thanks, Al

I now understand where the Right Shift + Num6 as described above likely comes from. On the Numpad, Num6 and Right Arrow are the same physical key, what you 'get' depends on whether NumLock is on or off. But I was not using that key at all as described above, but rather the stand-alone Right Arrow key. So it is not clear to me why MSFS identified the stand-alone RIght Arrow key as Num6 based on the timing of the Right Shift+Right Arrow combination. Al

When I want to enter the key combination Right Shift+Right Arrow under FSUIPC7 key assignments, I've noticed that I have to make sure I hit the Shift Right key a 'split second' before Right Arrow, or else FSUIPC7 only see the Right Arrow key. Conversely, in MSFS under the Keyboard Controls setup, when entering that same key combination into the Search by Input field, if I hit the Shift Right key a split second before Right Arrow, what gets entered into the search field is Right Shift+ Num6 ?? I don't know if this is a MSFS bug, or 'my' bug somehow., or what. However, if I hit the Right Arrow key a split second before Right Shift in MSFS, then the correct Right Shift + Right Arrow combination shows up in the search field. So MSFS and FSUIPC7 respond differently to this key combination depending on the split second timing when hitting the two keys. I'm posting here hoping someone might be able to help me understand all this. Thanks, Al

I check regularly but somehow missed the update to FSUIPC7 v7.02 -- just tried it, WORKS!! 😀 Thanks very much, Al

Hi John, Since a couple of months have passed now, I wondering if you have ever received any acknowledgement from Asobo that they are aware of the Simconnect/Numpad keys problem, and maybe some indication of when it might be fixed? Thanks, Al