Skip to content
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

Add an example scenario in the Readme #10

Closed
rdelassus opened this issue Sep 6, 2022 · 8 comments
Closed

Add an example scenario in the Readme #10

rdelassus opened this issue Sep 6, 2022 · 8 comments

Comments

@rdelassus
Copy link

rdelassus commented Sep 6, 2022

Hi, not so much an issue, but a way to figure out if I'm doing something wrong

I installed autokbisw and I see no difference with vanilla. I'm not sure if it isn't working properly or if I am doing something wrong.
There are no information in the readme about what is supposed to happen and when.

I imagine it's supposed to do something like that:

  • start typing with a keyboard 1 to make it active
  • select input source 1 for that keyboard
  • start typing with keyboard 2
  • select input source 2 for that keyboard

Now, when you type with keyboard 1, input source 1 is used (you can see it change on the upper right) and when using keyboard 2, input source 2 is used.

That's what I imagine is supposed to happen (but nothing happens here for me), but I can't be sure without a description.

@ohueter
Copy link
Owner

ohueter commented Sep 6, 2022

Hi @rdelassus, you are right about the way autokbisw should work. I'm currently having the same issue you described. The program itself works, unless when running as a service. I'll try to figure this out asap, as I'm affected myself ;-) In the meantime, you can download a binary from the release, and directly run it from the command line.

If you can spare some time, would you midn to add or re-write a section to/in the README in a more concise / understandable way? I would greatly appreciate some help there.

@rdelassus
Copy link
Author

PR #11 fixes this Issue

@rdelassus
Copy link
Author

Good luck with the bugfix

@ohueter
Copy link
Owner

ohueter commented Sep 7, 2022

Hi @rdelassus, thanks for the PR, I'll look into it later today. I (hopefully) fixed the issues with the app, please update the Homebrew tap and try again (brew install ohueter/tap/autokbisw and brew services start ohueter/tap/autokbisw). Make sure Homebrew installs the version 1.4.3 release. Please let me know if it works!

@rdelassus
Copy link
Author

rdelassus commented Sep 7, 2022

I installed 1,4,3, but he problem is not fixed on my part. There are some changes though. It used to do nothing. Now it does the following:

Note that I have a US keyboard on my macbook, and a french external keyboard. I do the setup as listed before (switch keyboard, switch input source).

On US input, whenever I press a key on either keyboard, I see the input source quickly switch to french then back to US. If I press very quickly (release before it switches back to US) then is stays in french, and this is now the new input source linked to that keyboard.

On french input source, it stays in french. Even if I use the shortcut (left ctrl + spacebar) to switch to US, it switches briefly and instantly goes back to french.

By playing a bit with which input source is linked to which keyboard and with the switch input shortcut, I can have the opposite behaviour happening.

I'm using karabiner too, not sure if it can produce some conflict as I don't know if it can control the input source

@ohueter
Copy link
Owner

ohueter commented Sep 7, 2022

Great to hear that at least something is happening now :-)

On my Macbook (internal DE keyboard, external US keyboard), it works as expected: When typing on the external US-layout keyboard, autokbisw switches to US layout. When pressing Ctrl+Space, MacOS switches to DE layout and autobisw saves DE as layout for this keyboard. Same when going back to US. Using the internal DE keyboard triggers the switch to DE layout. There is no jumping between the layouts while typing only on the same keyboard.

What I would recommend trying:

  • use the graphical switcher in the menu bar for initial setup to avoid pressing keys and triggering autokbisw
  • disable Karabiner temporarily to avoid any interference

@rdelassus
Copy link
Author

Everything works as expected when Karabiner is shutdown, and stops working when karabiner is started.
Thank you for the quick fix

@ohueter
Copy link
Owner

ohueter commented Sep 7, 2022

You're welcome! Glad that you could figure it out. I'll close this issue then.

@ohueter ohueter closed this as completed Sep 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants