Force Keyboard doesn’t work after Alfred restart

[pecheny]

This has already been reported

but nothing happened this bug still exists. It’s small but annoying.

 

I’ve ensured that the input sources checkbox is unchecked and no keyboard shortcuts for changing input sources are in conflict with Alfred’s.

 

Steps to reproduce:

1) Install this custom layout https://ilyabirman.ru/projects/typography-layout/download/ilya-birman-typolayout-3.6-mac.dmg  (maybe works with other custom keyboard layouts too, didn’t check)

2) Add “English - Ilya Birman typography” to the system

3) Set Alfred to force it

4) Check that the force works (it works)

5) Exit Alfred and reopen it

6) Check that the force works (it doesn’t)

Edited April 1, 2019 by pecheny

[Vero]

@pecheny Could you please try this using one of the built-in keyboard layouts and let me know whether the behaviour is normal? I've tested this in Mojave between built-in keyboard layouts, and the behaviour is as expected.

 

Check that you don't have "Automatically switch to a document's input source" ticked in System Prefs > Keyboard > Input Sources, and that you have specified Alfred's Force Keyboard Layout in the advanced prefs.

 

When you relaunch Alfred and go to the Advanced tab, is your custom keyboard layout still selected? What about when you use a built-in keyboard layout?

 

I'll move this into Discussion & Help to see whether anyone else can provide input as it seems specific to custom layouts.

 

Cheers,
Vero

[pecheny]

1. Yes, it works as expected with the built-in keyboard layout.

Quote

Check that you don't have "Automatically switch to a document's input source" ticked in System Prefs > Keyboard > Input Sources

I’ve already checked that at the time of writing, and mentioned it in the post

 

2.

Quote

When you relaunch Alfred and go to the Advanced tab, is your custom keyboard layout still selected?

Yes, it is still selected but forcing doesn’t work until i reselect it. It doesn’t happen with built-in layouts: they’re selected and forcing works.

Edited April 9, 2019 by pecheny

[pooolsker]

On 4/5/2019 at 4:04 PM, pecheny said:

1. Yes, it works as expected with the built-in keyboard layout.

I’ve already checked that at the time of writing, and mentioned it in the post

 

2.

Yes, it is still selected but forcing doesn’t work until i reselect it. It doesn’t happen with built-in layouts: they’re selected and forcing works.

 

Pecheny, did you find solution for that problem?

[Alexey_]

Hello!

 

I use my custom keyboard layout and face the same problem after every relaunch as I restart my computer pretty often.

 

 

[Andrew]

@Alexey_ could you update to the 4.6.2 b1279 pre-release, as I've made some changes to the way the force keyboard works.

 

From what I can gather, a number of 3rd party keyboards aren't reported by macOS to Alfred when he is first started, when Apple layouts and high quality 3rd party layouts are. I’ve made a change in b1279 where Alfred re-checks every time he is shown to see if the desired 3rd party keyboard is now available for use.

 

When starting Alfred b1279, if your desired keyboard isn't shown on first show of Alfred, try hiding and showing Alfred a few times to see if this now sets the correct keyboard, or if it indeed simply shows on first use.

 

Please let me know how you get on.