Summary of Issues Regarding inkcanvas in Windows AppSDK 1.7

[duwenlong2]

Hi, thank you very much for seeing the update of inkcanvas in the 1.7 update. The actual testing experience is very good.
But there are also some issues.

1. On an ARM machine with a 60Hz screen, I ran the ARM version with native compilation at a speed of 150mm/1s, resulting in a high write latency of an average of 23ms+. I am still trying to troubleshoot hardware issues.
2. I tried an Apple device and it had an average latency of 0-3.5ms at 120Hz. I don't know if this part will be optimized in the future updates of Windows AppSDK? Or will the interface for ink prediction be opened?
3. When will the Windows AppSDK 1.7 version update interfaces for brushes, dry and wet ink, and so on. When will there be an official release version?
4. We tested both Chinese and English for ink recognition;
   In a Chinese environment:
   The recognition rate for neat writing is 97%, and when I checked for italic writing, the recognition rate for diagonal writing was 90%. Writing a poem vertically is considered a word;
   Chinese English mixed writing: 15 English words and 75 Chinese characters. Can be recognized as a language. For example, after writing English, the remaining Chinese characters will be recognized as odd characters.
   The main scene is neat text written diagonally. Mixed writing of Chinese and English.
   When the language is Chinese, English will be recognized as a special symbol, and when the system language is English, Chinese will be recognized as a special symbol

5、May I ask if there have been any updates to ink handwriting on the Windows system in recent years? If so, where can I get updated logs.
6、Apple shared a feature for ink generation at WWDC. Will there be any related content in the update of inkcanvas? Or a discussion about how to achieve ink generation?