1 #  Multimodal Input Subsystem Changelog
2 
3 ##  cl.multimodalinput.1 Implementation Error of inputMonitor Corrected
4 
5 When **inputMonitor** is used to listen for **TouchEvent**, **TouchEvent** in the callback originally references the common **TouchEvent** of arkui-js, which is not exposed externally (that is, not exported). However, **TouchEvent** of arkui-ts is used by default in IDE. Therefore, the original API becomes invalid after the ArtTS syntax update. To solve this problem, you need to change the **TouchEvent** reference in **inputMonitor** to **TouchEvent** of the multimodal input.
6 
7 **Change Impact**
8 
9 The field name is changed. The value of the original field is **undefined**.
10 
11 **Key API/Component Changes**
12 
13 If you want to use **inputMonitor** to listen for **TouchEvent** of the multimodal input, you need to import the **touchEvent** class of the multimodal input separately.
14 
15 ```ts
16 import touchEvent from '@ohos.multimodalInput.touchEvent';
17 try {
18   inputMonitor.on('touch', (touchEvent: touchEvent.TouchEvent) => {
19     console.log(`Monitor on success ${JSON.stringify(touchEvent)}`);
20     return false;
21   });
22 } catch (error) {
23   console.log(`Monitor on failed, error: ${JSON.stringify(error, [`code`, `message`])}`);
24 }
25 ```
26 
27 **Adaptation Guide**
28 
29 Since OpenHarmony 4.0.11.5, change the field names of **TouchEvent** to those of the multimodal input.
30 
31 | Before Change        | After Change    |
32 | -------------- | ---------- |
33 | type           | action     |
34 | timestamp      | actionTime |
35 | deviceId       | deviceId   |
36 | globalX        | screenX    |
37 | globalY        | screenY    |
38 | localX         | windowX    |
39 | localY         | windowY    |
40 | force          | pressure   |
41 | touches        | touches    |
42 | changedTouches | touches    |
43