Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: ignore plain text (non-"shortcut") keystrokes #471

Open
amynbe opened this issue Mar 29, 2019 · 4 comments
Open

Feature Request: ignore plain text (non-"shortcut") keystrokes #471

amynbe opened this issue Mar 29, 2019 · 4 comments
Assignees
Labels
🔷Enhancement Type • Improvements for the software.

Comments

@amynbe
Copy link

amynbe commented Mar 29, 2019

When capturing a gif in a text editor, it would make more sense to only show keystrokes that don't appear directly in the text editor.
In other words, If I type a 1000-character text in my editor, I don't want the full text to appear in subtitles but only key strokes like:

  • tab
  • ctrl+v
  • enter
@NickeManarin NickeManarin self-assigned this Mar 29, 2019
@NickeManarin NickeManarin added the 🔷Enhancement Type • Improvements for the software. label Mar 29, 2019
@NickeManarin
Copy link
Owner

Nice request. :)

@zalmanlew
Copy link

Good idea, but there should be an option when applying keystrokes to ignore "plain text" which can be enabled/disabled.

There are programs (such as Illustrator or Photoshop) where regular keys toggle different tools etc.

@amynbe
Copy link
Author

amynbe commented Apr 3, 2019

But Illustrator and photoshop are not text editors, right? In those cases it would be easy to not use this feature and just delete your plain text from the existing key strokes dialog. That would work because there shouldn't be a lot of plain text, as opposed to the potential large amount of plain text that you would input in a text editor.

@amynbe amynbe closed this as completed Apr 3, 2019
@amynbe amynbe reopened this Apr 3, 2019
@b-a0
Copy link

b-a0 commented Jan 19, 2024

Looking for the same thing, would be a very nice addition!
Optionally this could be part of the key stroke editor where you could have a drop-down filter to select what type of key strokes (e.g. single characters, chords with 2 keys, chords with 3 keys, long presses, etc...) should be taken into account in the Key Strokes overlay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔷Enhancement Type • Improvements for the software.
Projects
None yet
Development

No branches or pull requests

4 participants