Qingtian
Qingtian
Thanks. So what you want is define `move` strictly as a combination of `take` and `insert`. All the cases above will be solved if we use `take` and `insert` instead...
This is a limitation of the native controls. Needs to check more to see how to get `focus` and `unfocus` events for all the controls.
@hiiamboris The WM_SETFOCUS message is a [nonqueued message](https://docs.microsoft.com/en-us/windows/desktop/winmsg/about-messages-and-message-queues#nonqueued-messages). It is sent directly to the control. We try to avoid having a WindowProc for every control, that's why some widgets don't...
Related issue: #5221
The trailing whitespaces at the end of each line are ignored by default. I don't have a strong use-case to support current behavior. So I'm OK to change it.
The position index is 1-based. `0` has no meaning. Maybe we should return `none`. ``` 1 2 3 4 5 6 7 8
Either the modify actions/natives reset the head or the read actions/natives check it.
> Great! > > You didn't implement any spec validation in this commit, right? No. No spec validation.
No problem when running inside Windows sandbox. So it seems like an issue with the hardware acceleration.
It seems that drawing too fast will crash D2D. Limit the refresh rate to 60 FPS, no freeze anymore on my Win11.