You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just one remark : when you use the "KeyDown" function, that would be great to deactivate the keydown (by sending a keyup) when your application window deactivate, for exemple you get focus on another window in the application switch to another app and to propose to remember the state when the window activates back.
Right now, if you simulate a SHIFT key down, when you switch to another window, the shift is still in use and, for exemple, this will select text up to the carret if you switch to text editing like window or application
The text was updated successfully, but these errors were encountered:
I get what you mean, but I have some reservations:
Unless I'm misunderstanding your last paragraph, the current behavior that you're describing is what happens when you're holding down the physical SHIFT key. In that sense, the library is accurately simulating the behavior of the physical key, which I think is desirable.
Changing the existing behavior (whatever that is) would potentially break client code, unless we are very careful to make the proposed change clearly opt-in.
I feel that keeping track of the application's window state is out of the scope of this library and should be implemented by client code at a higher level.
Hello ! Great stuff here !
Just one remark : when you use the "KeyDown" function, that would be great to deactivate the keydown (by sending a keyup) when your application window deactivate, for exemple you get focus on another window in the application switch to another app and to propose to remember the state when the window activates back.
Right now, if you simulate a SHIFT key down, when you switch to another window, the shift is still in use and, for exemple, this will select text up to the carret if you switch to text editing like window or application
The text was updated successfully, but these errors were encountered: