-
-
Notifications
You must be signed in to change notification settings - Fork 546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chaging language in system does not affect input in search #716
Comments
I cannot reproduce this by running macOS 14.3. Also using EN/RU layouts and changing is assigned to Caps Lock, which works just fine: Screen.Recording.2024-01-25.at.07.36.08.mov |
Maybe it's because changing is assigned to one key? Mine is CMD+SPACE. |
I tried changing the hotkey to ⌥Space and it still worked. |
I tried the following:
Maybe I should do some force settings reset for Maccy anyhow? Maybe the hotkey for Maccy somehow related - I have a setting to call it using SHIFT+⌥+C. |
I don't see anything suspicious in your settings.
I also use the same shortcut. Can you try playing around with different language change hotkeys and see if it helps? |
Hi, I'm Japanese. Another problem is here.
Then, the [Enter] key on step 3. should make just a selection of the word ideally, but it does close the Maccy window with an unintended clipboard item. I don't know the equivalent to Swift though, there is an "isComposing" property on JavaScript. I'm sorry for such a complicated issue there...😢 |
Hi @knoajp, thank you for sharing the exact steps - I can reproduce the problem with arrow/selection + enter and I'll fix it. What about the special key to change input? I can't find it on a keyboard viewer in macOS, can you point me to it? |
That Chinese screenshot is interesting. This could be another issue: when I use [^⇧Z] keys to activate Japanese IME on Maccy, I have to type some key at first to "make it ready for activation" or something. I suppose the caret has to be blinking when the [^⇧Z] keystrokes to be recognized. I did some research on the "regular way" topic here: https://softantenna.com/blog/maccy/ https://www.skri.gr.jp/2022/08/5945/ https://www.youtube.com/watch?v=qw3yuVdrZYw&t=1m12s (1:12) https://corp.logly.co.jp/blog/3181 And most Japanese people who use the US keyboard use Karabiner-Elements to convert [Left⌘]/[Right⌘] to [英数]/[かな]. |
Just pushed a commit that hopefully fixes the issue with changing layouts on a JIS keyboard. The arrow/enter issue is still present. |
Thank you for the latest 0.30.0 update! 🎉 Unfortunately, And then I don't know if this is a related issue or not, (Off-topic: The window position jumping bug seems to be fixed after this update) |
Frankly, I feel like the only solution for this would be to completely rewrite Maccy so it no longer uses NSMenu. That's a massive effort and I'm not sure when I would be able to start working on that. |
Okay, thank you for your kind support!!
Wow, that's strange. But on my Mac:
The [F6] key works as expected on other apps. And now the [Backspace] key works fine for me as well. I don't know why it didn't back then... |
I can probably prepare a build which will log all key presses and maybe we can debug if there is a different key being pressed. |
@knoajp If you are running Maccy 1.0.0, any chance you could also test 2.0.0.beta.7 and see if Japanese input is now handled correctly? |
It looks so good!! 🎉 |
Fixed in 2.0 |
Can confirm it fixed my problem also on maccy 2.0.1 + macos 15.0 |
Before Submitting Your Bug Report
Maccy Version (see 'About' window)
Version 0.29.4 (28)
macOS Version
14.2.1 (23C71)
Maccy Settings
Description
Calling the Maccy input window and changing the language, does not affect the language itself in search input dialog.
I have RU and EN keyboard layout settings in the system only.
Steps to Reproduce
Actual behaviour:
The changed system keyboard layout is not taken to the account in maccy search dialog.
I've noticed, that in macOS 13 it worked properly, but in macOS 14 is not.
Screen.Recording.2024-01-25.at.13.54.56.mov
The text was updated successfully, but these errors were encountered: