IPhone simulated touch screen implementation event tutorial

IPhone touch screen SimulationImplementationEventThe tutorial is the content introduced in this article. Let's take a look at the content first. Now I have another ideaIPhoneThe idea of assisting in debugging is, of course, nothing about control, that is, to make some assistance on the screen, the assisted party should also perform the same operation, due to the uncertainty of the program to be debugged, it can only be used to send various screen-targetedSimulated Event.

Because apple did not release direct sendingTouch screen eventsSo I am using a jailbroken iPhone with PrivateFramework, and I am not expecting to go public. It is for internal debugging.

First, unplug the header file of the private framework from the kennytm website. For this application, you only need the GrapicsServices folder and Availability2.h. Import GraphicsService. framework under Platforms under the Xcode directory. The preparation is OK.

To send event messages, we mainly construct GSEventRecord. For simple events, we only need to fill in the type parameters in GSEventRecord. If it is more complex, we need to fill in the structure behind it, the fill size must be specified in the infoSize parameter.

C code

 
 

  
  
typedef struct GSEventRecord {     
  
  
    GSEventType type; // 0x8     
  
  
    GSEventSubType subtype; // 0xC     
  
  
    CGPoint location;   // 0x10     
  
  
    CGPoint windowLocation; // 0x18     
  
  
    int windowContextId;    // 0x20     
  
  
    uint64_t timestamp; // 0x24, from mach_absolute_time     
  
  
    GSWindowRef window; // 0x2C     
  
  
    GSEventFlags flags; // 0x30     
  
  
    unsigned senderPID; // 0x34     
  
  
    CFIndex infoSize; // 0x38     
  
  
} GSEventRecord;    
  
  
 
  
  
typedef struct GSEventRecord {  
  
  
 GSEventType type; // 0x8  
  
  
 GSEventSubType subtype; // 0xC  
  
  
 CGPoint location;  // 0x10  
  
  
 CGPoint windowLocation; // 0x18  
  
  
 int windowContextId; // 0x20  
  
  
 uint64_t timestamp; // 0x24, from mach_absolute_time  
  
  
 GSWindowRef window; // 0x2C  
  
  
 GSEventFlags flags; // 0x30  
  
  
 unsigned senderPID; // 0x34  
  
  
 CFIndex infoSize; // 0x38  
  
  
} GSEventRecord; 
 
 

The header file does not provide some convenient methods to construct complex information structures, which is really different from the public API. However, some very simple messages can still be called directly, such as void GSEventLockDevice (); It is equivalent to constructing a GSEventRecord structure with the type of kGSEventLockDevice and then sending it out.

In a slightly complex example, we send a "Press" command to the {50, 50} coordinates of the screen.

C code

 
 

  
  
#import "GSEvent.h"     
  
  
#include <mach/mach_time.h>     
  
  
void sendclickevent(){     
  
  
    mach_port_t thePortOfApp = GSCopyPurpleNamedPort("com.fuckyou.fuck");     
  
  
         
  
  
    GSEventRecord header;     
  
  
    GSHandInfo click;     
  
  
    GSPathInfo pathInfo = {2,2,2,1,1,{50,50}, NULL};     
  
  
         
  
  
    bzero(&header, sizeof(header));     
  
  
    bzero(&click, sizeof(click));     
  
  
    
  
  
    header.type = kGSEventHand;     
  
  
    header.subtype = kGSEventSubTypeUnknown;     
  
  
    header.location.x = 50;     
  
  
    header.location.y = 50;     
  
  
    header.windowLocation.x = 50;     
  
  
    header.windowLocation.y = 50;     
  
  
    header.infoSize = sizeof(GSHandInfo)+sizeof(GSPathInfo);     
  
  
    header.timestamp = mach_absolute_time();     
  
  
    
  
  
    click.type = kGSHandInfoTypeTouchDown;     
  
  
    click.deltaX = 1;     
  
  
    click.deltaY = 1;     
  
  
    click.pathInfosCount = 1;     
  
  
         
  
  
    struct    
  
  
    {     
  
  
        GSEventRecord record;     
  
  
        GSHandInfo hand;     
  
  
        GSPathInfo path;     
  
  
    } record = {header, click, pathInfo};     
  
  
         
  
  
    GSSendEvent(&record, thePortOfApp);     
  
  
}    
  
  
 
  
  
#import "GSEvent.h"  
  
  
#include <mach/mach_time.h> 
  
  
void sendclickevent(){  
  
  
    mach_port_t thePortOfApp = GSCopyPurpleNamedPort("com.fuckyou.fuck");  
  
  
      
  
  
    GSEventRecord header;  
  
  
    GSHandInfo click;  
  
  
    GSPathInfo pathInfo = {2,2,2,1,1,{50,50}, NULL};  
  
  
      
  
  
    bzero(&header, sizeof(header));  
  
  
    bzero(&click, sizeof(click));  
  
  
 
  
  
    header.type = kGSEventHand;  
  
  
    header.subtype = kGSEventSubTypeUnknown;  
  
  
    header.location.x = 50;  
  
  
    header.location.y = 50;  
  
  
    header.windowLocation.x = 50;  
  
  
    header.windowLocation.y = 50;  
  
  
    header.infoSize = sizeof(GSHandInfo)+sizeof(GSPathInfo);  
  
  
    header.timestamp = mach_absolute_time();  
  
  
 
  
  
    click.type = kGSHandInfoTypeTouchDown;  
  
  
    click.deltaX = 1;  
  
  
    click.deltaY = 1;  
  
  
    click.pathInfosCount = 1;  
  
  
      
  
  
    struct  
  
  
    {  
  
  
        GSEventRecord record;  
  
  
        GSHandInfo hand;  
  
  
        GSPathInfo path;  
  
  
    } record = {header, click, pathInfo};  
  
  
      
  
  
    GSSendEvent(&record, thePortOfApp);  
  
  
} 
 
 

It should be noted that an application must receive the port, that is, the first line of code, to send events to an application. However, to send complex information, you must splice several pieces of information together. It is more appropriate to define a structure for writing and enter the size of the information body correctly, these skills seem to have returned to the wild age. I saw a 0-long array and constructed the structure on the heap. However, the processing of these messages is asynchronous, and I don't know when the memory can be safely recycled, therefore, we recommend that you use the structure concatenation method.

In addition to the touch screen, another important thing is the keyboard input, but the iPhone input is not very special, it is said that the keyboard input, it means that.

The specific encoding process is actually no different from that of a touch screen event. However, if the structure name of a keyboard event, such as GSHardwareKeyInfo or GSKeyInfo, appears to be searched by google, no result is returned, at the beginning, I still wanted to get together. It took two or three days to get together and I couldn't find out that it could actually be reversed. I used GSEventCreateKeyEvent to create a keyboard event, and then I parsed it, so I got it done in this way, and sadly, I think too much about it, and the vast majority of the members can fill in 0. There is no need to worry about coding areas.

Objective-c code

 
 

  
  
GSEventRecord header;     
  
  
GSHardwareKeyInfo key = {0,0,0,0,1,{'a'},1,{'a'},0,0,0,0};     
  
  
memset(&header, 0, sizeof(header));     
  
  
    
  
  
header.type = kGSEventKeyDown;     
  
  
header.infoSize = sizeof(GSHardwareKeyInfo);     
  
  
header.timestamp = mach_absolute_time();     
  
  
    
  
  
struct     
  
  
{     
  
  
    GSEventRecord header1;     
  
  
    GSHardwareKeyInfo key1;     
  
  
}fuck = {header, key};     
  
  
GSSendEvent(&fuck, GSGetPurpleApplicationPort());    
  
  
 
  
  
    GSEventRecord header;  
  
  
    GSHardwareKeyInfo key = {0,0,0,0,1,{'a'},1,{'a'},0,0,0,0};  
  
  
    memset(&header, 0, sizeof(header));  
  
  
      
  
  
    header.type = kGSEventKeyDown;  
  
  
    header.infoSize = sizeof(GSHardwareKeyInfo);  
  
  
    header.timestamp = mach_absolute_time();  
  
  
      
  
  
    struct  
  
  
    {  
  
  
        GSEventRecord header1;  
  
  
        GSHardwareKeyInfo key1;  
  
  
    }fuck = {header, key};  
  
  
    GSSendEvent(&fuck, GSGetPurpleApplicationPort()); 
 
 

In this way, you can enter a, provided that the cursor must be in the input box.

Of course there are still many problems in the future. This is actually just an event that your program sends to itself. What needs to be done later is to send events to the front-end program or even the main interface when the program is running on the background. Can you do this, i'm not sure.

Summary:IPhone touch screen SimulationImplementationEventI hope this article will help you with the introduction of this tutorial! For more information, see edit recommendations.