Skip to content

fix: ignore accidental short hold recordings - #56

Open
TimInTech wants to merge 2 commits into
mainfrom
fix/hold-short-press-recovery
Open

fix: ignore accidental short hold recordings#56
TimInTech wants to merge 2 commits into
mainfrom
fix/hold-short-press-recovery

Conversation

@TimInTech

Copy link
Copy Markdown
Owner

Zusammenfassung

  • verwirft versehentliche Hold-Tastendrücke unter 150 ms ohne Transkription
  • behandelt leere Transkripte über ein eigenes No-Speech-Signal ohne persistenten roten Fehlerzustand
  • aktualisiert deutsche und englische README-Dokumentation

Verifikation

  • Ubuntu 26.04 GNOME/Wayland live: 0,126 s und 0,133 s verworfen; normale Aufnahme/Auto-Paste erfolgreich
  • 531 passed, 2 skipped
  • Python-Syntaxprüfung bestanden
  • git diff --check sauber

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8005b49545

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread app/hotkey_service.py
"Accidental hold press ignored: %.3fs < %.3fs",
held_seconds, MIN_HOLD_PRESS_SECONDS,
)
self.recording_discard.emit()

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Clear the debounce after discarding a short hold

When a press shorter than 150 ms is discarded, last_trigger[workflow] still contains the key-down timestamp, so an immediate corrective press within DEBOUNCE_SECONDS (600 ms) is silently rejected by the debounce check and never starts recording. Clear that workflow's debounce entry when emitting recording_discard, or otherwise exempt the next key-down after a discard.

Useful? React with 👍 / 👎.

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

Successfully merging this pull request may close these issues.

1 participant