Implementation of Native Touch Passthrough and Better Gesture Recognizing

[TrueZhuangJia]

Hello everyone,

I've been waiting for a true native-touch oriented version of moonlight-iOS for so long, that I have to fork it myself. Here's the changes made in my fork:

1. The native touch passthrough coded following the logic of moonlight-android.
   
   One of the key challenge is, iOS does not offer a pointerId attribute for UITouch object like android.
   I use a dictionary & a set for mapping UITouch object memory address to pointerId, which was generated from arc4random(), with a mechanism to prevent collision.
   Related codes are placed in NativeTouchHandler.m . Here's how native touch works out now:
   
   
   
   
   

2. Refactored Better Session Exit Gesture Recognition to Prevent Accidental Exits.
   
   I suggest, if we implement native multi-touch on moonlight-iOS, preventing unexpected session exit is a must-have feature.
   Unlike the official moonlight which serves as a streaming client for mainly game controller players, native touch player like me needs to perform intense touch operation on screen, which triggers the original exit gesture recognition unexpectedly, it's so frustrating if you suddenly exit the remote desktop during gameplay.
   So I wrote a recognizer to replace the iOS native API, requiring a swipe from the screen edge to a certain distance to trigger the exit to the desktop. The trigger threshold for the swipe distance and which edge to start the swipe from have been added to the settings menu. For user who prefers the original way, just set distance to 0.
   
   
   And this is how it works:
   
   Related codes are placed in CustomEdgeSwipeGestureRecognizer.m, this custom defined recognizer is added to StreamFrameViewController.
   
   
   
   

3. Refactored Better Tap Gesture Recognition for Reliable Local Keyboard Toggle.
   
   I read a comment from the maintainer that conflict between 3-finger keyboard toggling & android gesture is one of the reasons why native-touch is not enabled on official moonlight-android yet. My answer to that question is adding configurable finger number for the user to decide.
   On iOS however, there're additional issues if you wanna implement the same multi-finger tap keyboard toggle:
   The official version of Moonlight-iOS triggers the local keyboard switch when it detects three touch points on the screen, a mechanism that makes three-point dragging interrupted by the showing up of keyboard.
   I also tried UITapGestureRecognizer provided by iOS native API: the success rate of gesture recognition would decrease, and even continuous failures could occur.
   Therefore, I rewrote a TapGestureRecognizer with a recognition rate of almost 100% ， and having no affect on multi-point dragging（keyboard invoked on all-fingers-up, with a down time threshold limitation, similar to moonlight-Android）
   To prevent local keyboard from being invoked unexpectedly, I add the required number of fingers for tap recognizer to the setting menu like my android fork. It is recommended to set 3-finger triggering on phones and 4 or more on tablets (as your palm might touch the screen, forming a third touch point when using a tablet).
   
   Here's a *.gif example of setting "Fingers to Tap" to 4 on my ipad mini6:
   
   Related codes are placed in CustomTapGestureRecognizer.m, this custom defined recognizer is added to StreamView.

My ipad mini6 is on iOS 17.2, I missed the trollstore and there's no jailbreak yet. Please consider reviewing or even merging my implementation into the official version, Sideloading app on iOS and the 7 day refresh is just, painful.

Thank you for your attention~