The logic of current TheWay will cause issue when you try to let TheWay override an A-route attack waypoint back to steerpoint. For example, if someone designated his 1A waypoint to be 1.A (attack point), then he attempts to use TheWay to input A route waypoint again, he will get stuck at overriding "1A" with "1.A" when he press PB1.
This is due to the logic of F-15E that attack waypoints and steerpoints are actually "different" in the avionic. You can not obsfucate it when trying to input. The only way of interchanging a attack waypoint with a steerpoint is:
- Type in the correct name of the point, if it is 1A, type 1A. If it is been designated 1.A, press 1.A, not anything else.
- After the point is properly selected, input the exact number and letter of your waypoint, but this time with(or without) the dot only.
- Now you should see it change from 1A to 1.A or vice versa.
And that means you have to never assume a point's identity, if it is changed into a attack waypoint by a user, then the original method of TheWay, which is input a steerpoint, will cause an error when trying to call the point with the incorrect type.
This has no simple and comprehensive solution, but should aware the user with this problem. A possible solution is we designate A route to be steerpoint route and B route to be attack point route, which could also enable the function of directly input the point to JDAMs (as shown in the pull request)
The logic of current TheWay will cause issue when you try to let TheWay override an A-route attack waypoint back to steerpoint. For example, if someone designated his 1A waypoint to be 1.A (attack point), then he attempts to use TheWay to input A route waypoint again, he will get stuck at overriding "1A" with "1.A" when he press PB1.
This is due to the logic of F-15E that attack waypoints and steerpoints are actually "different" in the avionic. You can not obsfucate it when trying to input. The only way of interchanging a attack waypoint with a steerpoint is:
And that means you have to never assume a point's identity, if it is changed into a attack waypoint by a user, then the original method of TheWay, which is input a steerpoint, will cause an error when trying to call the point with the incorrect type.
This has no simple and comprehensive solution, but should aware the user with this problem. A possible solution is we designate A route to be steerpoint route and B route to be attack point route, which could also enable the function of directly input the point to JDAMs (as shown in the pull request)