Allow coordinates input for JDAMs of F-15E

[WangNorthSea]

Added a new dialog 'Input for JDAMs?' for F-15E to input the coordinates as TGT points and transfer to JDAMs.

Before doing that, the user must make sure that:

1. Right MPD is on Smart Weapons Page.
2. Better used 'NXT STA' to change the selected bomb.
3. Better not program the bomb first.
   

Both front seat and rear seat supported.
The video below shows the entire process:
https://www.bilibili.com/video/BV1s94y1J7jL/

[blueberrypi-studio]

I'd love to see this as an implementation application wide, but instead of with more dialogues, added under the drop-down where you have:

• From F10 Map
• Input weapons
• From file

Or a check box to import it to weapons somewhere on the screen

Especially since the F-15E already has quite a few dialogues

Nice work

[WangNorthSea]

I'd love to see this as an implementation application wide, but instead of with more dialogues, added under the drop-down where you have:

• From F10 Map
• Input weapons
• From file

Or a check box to import it to weapons somewhere on the screen

Especially since the F-15E already has quite a few dialogues

Nice work

That would be better, but providing this feature for all models requires a lot of work, and considering that some models have multiple smart weapons, and not all of them have PP mode.
I developed this feature for the F-15E only because at this stage, inputting TGT point coordinates for each bomb is really troublesome.

[blueberrypi-studio]

Oh 100%

A more modular approach (which @aronCiucu my use) would allow other devs to develop that, I'd imagine your code would be mostly the same, just the entry point is different.

(I'm not criticizing your work don't worry)

I feel this is a very good feature, and as a general rule I think this should be modular so it can be implemented in more planes

[WangNorthSea]

Oh 100%

A more modular approach (which @aronCiucu my use) would allow other devs to develop that, I'd imagine your code would be mostly the same, just the entry point is different.

(I'm not criticizing your work don't worry)

I feel this is a very good feature, and as a general rule I think this should be modular so it can be implemented in more planes

That makes sense. What I can think of now is to provide a function that passes in parameters such as model, device codes, and button codes, and then adds some weapon input operations to the 'payload' based on different models.
I will try to implement this way later.

[blueberrypi-studio]

Don't stress it, hopefully we can bribe @aronCiucu to come up with am ingenious solution to give this an entry point, this has been a hotly demanded feature on the hornet for years.

The beauty of this app is once you've got an entry point, it's very easy to develop

(For me anyway, I've struggled to understand how the back end stuff works, and don't want to try in case I mess it up)

Been trying to get VR support for a while, but EDs whacky GUI code has been stopping me so far

[aronCiucu]

Hello, good work, I have some questions about the code changes, most notably about the lua file. Could you please elaborate on the reasoning behind those?

[WangNorthSea]

Hello, good work, I have some questions about the code changes, most notably about the lua file. Could you please elaborate on the reasoning behind those?

Sorry, the code in the Lua file is indeed confusing. The reason I made changes to this file is that I found a problem with the existing key delay method when entering PP MSN in the F/A-18C. It seems like a bug of the F/A-18C that requires a wait time, such as 50ms, after pressing and releasing a key before the next key can be pressed. Otherwise, there will be anomalies in the subsequent coordinate inputs. The changes in the Lua file are meant to wait for a period after completing a key action before executing the next action. I didn't know how to add new fields in 'payload,' so I reused the string 'addDepress.'

I'm not very familiar with PRs of GitHub, and I didn't expect that the new commits would also be included. The code changes are indeed significant and not very elegant. Although I received appreciation from many Chinese players for the new feature after creating a demo video, if you feel that these changes would impose a significant burden on you, you can choose to close this PR. Alternatively, you can use a portion of the code here to implement it more effectively.

[blueberrypi-studio]

When you pull request you pull request the whole branch, so to not include changes but them on a different branch and that should solve that :-)

[Selmaks]

Any chance we can get this merged please? I would really like to use the PP MSN in the F/A 18. I tried @WangNorthSea build it seems to work ok apart from the options cog when pressed theway app disappears.