Windows key and Ctrl+Windows are not recognized as shortcuts

(#874) Bug Needs triage desktop voice

Observed behaviour

On Windows, global shortcuts that use the Windows key are not recognized by Fluxer. In particular, Ctrl+Windows does not work as a shortcut, and assigning the Windows key by itself also does not work. This prevents using these bindings to mute/unmute or use push-to-talk while speaking in another app (for example, Wispr Flow). Other shortcut combinations work. Expected: the configured Windows-key shortcut should trigger the selected voice action globally, including while Fluxer is unfocused, subject to Windows-reserved shortcuts.

Reproduction steps

  1. Open Fluxer Desktop on Windows and join a voice channel.
  2. In keybind settings, assign the desired voice action (for example, Toggle Mute or Push to Talk) to Ctrl+Windows.
  3. Focus another app and press Ctrl+Windows; observe that Fluxer does not trigger the action.
  4. Repeat with the Windows key by itself as the configured shortcut; it also does not trigger the action.

Build information

Windows desktop app; exact Fluxer build/version not provided

Platform

macOS, Windows, Linux

Evidence

Related: #78 reports a global Toggle Mute shortcut failure on Windows and is closed. This report is specifically about bindings containing the Windows key: Ctrl+Windows and Windows alone. Windows version, exact Fluxer build, and whether this occurs in every voice action: not provided yet.

1 comment

Sign in with Fluxer to comment and vote.
Comment by @cerealdevv
RexSystem 1 vote originally by @cerealdevv on GitHub
if i'm not mistaken, the super/windows key is very hard to bind on apps on windows