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
Since updating to 5.4.0 just now, I noticed that there is a small delay between hitting arrow keys to navigate menus and the menu updating. I also did a direct comparison with 5.2.0 and that feels much snappier.
This also applies to hovering items with the pointer, but it's less of an issue there since you are in direct control of the pointer and the pointer itself updates fast enough to your movements.
The text was updated successfully, but these errors were encountered:
No it's fine, I think this is a more appropriate place to discuss it anyway since it's a valid concern.
Are you sure about that? It's most certainly not like this in any text editor I've used in the last decade and I don't see why it would be. Which applications are you thinking of that operate on keyup?
It's a standard practice to bind event handlers to full key presses, at least on the web front end. There's some shortcut stuff you can't implement if you bind to downs, but that is rarely used. I myself usually use only downs as it feels faster. I assumed I had some reason to bind to up in recent menu shortcut handling refactor, but looking at the code I don't see any, so I'll set it back to downs.
Since updating to 5.4.0 just now, I noticed that there is a small delay between hitting arrow keys to navigate menus and the menu updating. I also did a direct comparison with 5.2.0 and that feels much snappier.
This also applies to hovering items with the pointer, but it's less of an issue there since you are in direct control of the pointer and the pointer itself updates fast enough to your movements.
The text was updated successfully, but these errors were encountered: