Closing the input views changes the current language

[Nemoumbra]

Describe the bug
For example, renaming a variable opens a small window called "Rename local variable". If you switch the language (Win+Space / Alt + Shift) while the window is open, then close the window (doesn't matter how), the language reverts back to the language from before the window was opened.

I don't see why this transactional behavior would be of any use. This is kind of annoying even... Imagine you're writing to someone in, say, Spanish, then you switch to Ghidra, decide to rename something, notice that your language is wrong, switch to English, rename it, then decide to rename another entity and notice that your language is Spanish, again.

Expected behavior
Ghidra is not supposed to interfere with the language settings.

Environment (please complete the following information):

• OS: Windows 10
• Java Version: 21
• Ghidra Version: 11.4.2
• Ghidra Origin: official GitHub distro

[dragonmacher]

I cannot reproduce the behavior in my environment.

Ghidra does not have any code related to input methods or languages. My guess is that this is an issue between the OS and the JVM.

[Nemoumbra]

Guess this will stay undebuggable, unless I build pull and rebuild Ghidra myself. Which places should I pay attention to? I guess it could be related to some window methods.

[dragonmacher]

Since we do not manage Input Methods, this will be very hard to debug, as it requires the debugging of Java code.

My hope is that other users more familiar with this may offer more ideas for workarounds. If that happens, we may be able to add code to our system to avoid the Java issue.

[github-klugr]

Could be this Windows setting...
https://www.tenforums.com/tutorials/102999-turn-off-use-different-keyboard-layout-each-app-window.html