Keyboard Manager remaps don't work consistently with FZ and other modules

[arjunbalgovind]

KBM currently does not always work consistenly with FZ and Shortcut guide if the Win key is remapped. The current workaround for a user would be to disable and enable KBM (since this will restart the hook), however we should automatically do this for v1.

[arjunbalgovind]

Also applies to all the other PowerToys that use low level hooks i.e. PT Run, Color Picker and any future ones.

[arjunbalgovind]

Fixing this would also fix #4205 and #4360

[crutkas]

Wouldn't the #6060 work help correct this issue. @enricogior as FYI

[arjunbalgovind]

It won't since KBM and SG wouldn't be running out of the centralized handler. Since these still have independent hooks we need to ensure that the KBM hook is restarted whenever any of them gets enabled.
As @yuyoyuppe suggested offline in a mail thread, using IPC would be the best way to do this.

[dedavis6797]

@jaimecbernardo this appears to be a large work item. Can we investigate the remaining work for this in 0.47? We don't have to try to resolve this by 0.47, I'd just like a better understanding of the timeline since this keeps getting bumped.

[jaimecbernardo]

@dedavis6797 ,

I've tried replicating this but without success. I've remapped the Win key and then tried to use the shortcuts for FancyZones and Shortcut Guide without success (as expected).

So what's the issue here? It might have been fixed given all the changes in KBM, FancyZones and Shortcut Guide since then. Opened issues relating to this issue seem to have been closed since then as well.

@arjunbalgovind , how can we replicate this?

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

[arjunbalgovind]

@jaimecbernardo I'm not able to repro this anymore. This used to happen when all the keyboard hooks used to run from the main runner process. Seems like this was fixed as a result of #10127 probably since it runs at a higher priority. I think the issue can be closed.

[jaimecbernardo]

Thank you!