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
@AdminHcat thanks! I also notice this issue, and I agree, it is annoying.
I will try harder to fix this because my previous attempts not succeed, and I still don't understand the cause 🙁
This is an attempt to fix the issues that sometimes arise when renaming functions or variables using the "n" shortcut as stated in issue skylot#1440.
The reasoning behind the change: The instance creation of the RenameDialog was somehow affecting the UI thread and not allowing for the key release event to be dispatched. By running everything inside the invokeLater block, this might get fixed as it will execute after all previous tasks are finished.
We now also only show the dialog after EVERYTHING is set up, not before.
…(PR#2075)
This is an attempt to fix the issues that sometimes arise when renaming functions or variables using the "n" shortcut as stated in issue #1440.
The reasoning behind the change: The instance creation of the RenameDialog was somehow affecting the UI thread and not allowing for the key release event to be dispatched. By running everything inside the invokeLater block, this might get fixed as it will execute after all previous tasks are finished.
We now also only show the dialog after EVERYTHING is set up, not before.
When using the rename shortcut key N, there is a probability to enter it
There have been many times. When you press the N key, n appears instead of the original name
The following is the keyboard test software, indicating that the keyboard is pressed only once
The text was updated successfully, but these errors were encountered: