How do I directly type into an app's text field? #896
Replies: 2 comments 2 replies
|
What you are seeing is the intended flow rather than a setting that is switched the wrong way, so it is worth knowing why before hunting for a toggle. FluidVoice does not type into the target app as you speak. It captures where your text should go before it shows anything, then puts the finished text there in one go at the end. The comment in private func captureRecordingTargetContext() {
// Capture the focused target PID BEFORE any overlay/UI changes.
// Used to restore focus when the user interacts with overlay dropdowns.
let focusTarget = TypingService.captureSystemFocusTarget()That capture exists because the overlay necessarily steals focus while you dictate. The text appearing in the overlay first is a preview of the transcription in progress, controlled by One thing worth separating from the design question: if the second hotkey press feels like an extra step rather than "stop recording", or if text sometimes lands in the wrong app, check that FluidVoice has Accessibility permission in System Settings → Privacy & Security. Both the focus capture and the synthetic Cmd+V depend on it, and when it is missing or was granted to an older copy of the app the insertion half degrades while the recording half keeps working — which looks exactly like text getting stuck in the overlay. |
|
Yeah, typing it directly would cause problems in fixing your mistakes, which happens after that. So the right way is to show what you talk in the box first and then it goes into the field once you're done. |
Uh oh!
There was an error while loading. Please reload this page.
For example I am trying to type directly into a TextEdit opened file, but the text is not being typed directly in the file but first on app overlay and then when click the hotkey it goes to the TextEdit file. What settings need to be changed so that voice input directly types text into an editable text field on the mac?
All reactions