This section mainly introduces the methods for handling interactions with mouse, keyboard, and touch screen.
Mouse
The above figure shows the conversion flow of mouse messages in CAR interaction. From the above, the Application is a self-service application uploaded by the business side in the console, which runs on the Windows system and responds to mouse window messages from Windows. When the business side accesses the SDK to send mouse messages, it needs to convert the messages from the platform where the SDK is running into mouse messages to operate the application.
In general, the situations that each platform deals with are as follows:
On Android and iOS platforms, the touch messages from the system are converted to CAR mouse messages.
On Web pages, depending on the system on which the page is running, mouse messages are converted to CAR messages when the Web page is running in a Windows/macOS browser, and touch messages are converted to CAR messages when the Web page is running in an Android/iOS browser.
Among them, the conversion of touch messages to CAR mouse messages usually involves converting a single finger click to a CAR mouse click, a single finger swipe to a CAR mouse move, and so on.
Therefore, the business side needs to be adapted according to the SDK used and the platform running. For more details, please refer to the following:
The above figure shows the conversion flow of keyboard messages in CAR interaction. From the above, the Application is a self-service application uploaded by the business side in the console, which runs on a Windows system and responds to keyboard window messages from Windows. When the business side accesses the SDK to send keyboard messages, it needs to convert the messages from the platform where the SDK is running into keyboard messages to operate the application.
In general, the situations that each platform deals with are as follows:
On Android and iOS platforms, the system's touch messages or soft keyboard messages are converted to CAR keyboard messages.
On Web pages, depending on the system on which the page is running, keyboard messages are converted to CAR keyboard messages when the Web page is running in a Windows/macOS browser, and touch messages or soft keyboard messages are converted to CAR keyboard messages when the Web page is running in an Android/iOS browser.
Among them, the conversion of touch messages or soft keyboard messages to CAR messages usually involves converting touch steering wheel operations to WASD messages of the CAR keyboard, converting soft keyboard messages directly to CAR keystroke messages, and so on.
Therefore, the business side needs to be adapted according to the SDK used and the platform running. For more details, please refer to the following:
The above figure shows the conversion flow of touch messages in the CAR interaction. From the above, the Application is a self-service application uploaded by the business side in the console, which runs on the Windows system and responds to touch window messages from Windows. When the business side accesses the SDK to send touch messages, it needs to convert the messages from the platform where the SDK is running into touch messages to operate the application.
In general, the situations that each platform deals with are as follows:
On Android and iOS platforms, the touch messages from the system are converted to CAR touch messages.
Converting touch messages to CAR touch messages when the web page is running in an Android/iOS browser only.
It is recommended that the business side can use the SDK to convert touch messages from their platform to CAR touch messages only if the application supports Windows touch window message processing and the application tests well on a physical Windows touch screen device.
Note：
It is not recommended to use the mouse-to-touch of UE or Unity engine to test whether the application software handles the touch messages normaly, because the touch behavior will be abnormal on the touch screen device.
Therefore, the business side needs to be adapted according to the SDK used and the platform running. For more details, please refer to the following:
