[area] 快捷键占用右ctrl后会导致其他组合键失效

[huoranxuanyuan]

现象

选择长按进行语音识别时右ctrl键被完全占用，无法发出其他组合按键

影响

正常输入文件QQ及微信发送消息使用ctrl+enter的方法进行发送，但有些时候单手操作使用右ctrl+enter进行发送，目前ctrl会被语音完全占用，导致只能识别到一个enter无法发送消息

建议接受标准

优化快捷键占用的逻辑，当选择长按快捷键进行语音输入时，点按不会触发功能

TODO / 不确定项

No response

[H-Chris233]

这个似乎做不到，除非牺牲用户体验(点按之后要等一会才能启动),你可以尝试切换到其他快捷键。

[Cooper-X-Oak]

This was generated by AI during triage.

Triage Notes

What we've established so far:

• This feedback is about hotkey product policy rather than a confirmed implementation bug: when Right Ctrl is used as push-to-talk, it can conflict with app-level shortcuts such as Right Ctrl + Enter in QQ/WeChat.
• The issue currently has wontfix, but the label alone is not enough for beta users because it does not explain the tradeoff or give them a practical workaround.
• Follow-up tracking issue: [hotkey/policy] 说明右 Ctrl 占用策略并提供替代路径 #485.

Proposed explanation / alternative path for maintainer approval:

• If OpenLess reserves a single modifier key as push-to-talk, that key may need to be consumed while the app decides whether to start/stop recording. This can conflict with shortcuts that use the same physical key.
• Recommended user workarounds: choose a non-conflicting OpenLess hotkey, avoid Right Ctrl if Right Ctrl + Enter is part of the user's chat workflow, or use toggle mode where appropriate.
• If we decide this should not remain wontfix, the implementation should be split into a separate design issue covering tap-vs-hold threshold, combination-key passthrough, and regression gates.

[Cooper-X-Oak]

This was generated by AI during triage.

Decision

We are keeping this as wontfix for the current beta patch, with an explicit explanation and workaround instead of changing hotkey behavior.

Why:

• On Windows, OpenLess uses a low-level keyboard hook for modifier-only recording keys such as Right Ctrl.
• In push-to-talk mode, the configured key is intentionally reserved while recording so OpenLess can start on key down and stop on key up.
• Because of that, Right Ctrl + Enter in apps such as QQ / WeChat can be seen by the target app as Enter only while Right Ctrl is reserved.
• Making a tap pass through while hold still records would require a new delayed tap-vs-hold design, which would change the instant push-to-talk feel and needs a separate product/design issue.

Recommended workaround:

• Prefer the default Toggle mode: press Right Ctrl once to start, press it again to stop. This avoids holding Right Ctrl while sending messages.
• If you want to keep push-to-talk, choose a recording shortcut that is not part of your chat send shortcut.

Implemented follow-up:

• The Recording settings page now shows a warning only for the conflict case: Windows + Right Ctrl + Push-to-talk.
• The Windows default remains Right Ctrl + Toggle. We are not changing defaults and not blocking users from choosing Right Ctrl + Push-to-talk.