mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #471] Feature Request: ignore plain text (non-"shortcut") keystrokes #392
Labels
No labels
copy cats
duplicated
future feature
pull-request
⬜ Accepted
⬜ Completed
⬜ Help Wanted 💪
⬜ In Progress
⬜ Missing Details
⬜ Pending
⬜ Waiting For Answer ⏳
🆕 feature preview
🔷 Bug 🐛
🔷 Out Of Scope
🔷 Out Of Scope
🔷 Question
🔷Enhancement
🔷Enhancement
🔷Invalid / External
🔷Knowledge Base
🔷Won't Fix
🕑 High
🕑 High
🕑 High
🕕 Medium
🕙 Low
🕛 Critical
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ScreenToGif#392
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @amynbe on GitHub (Mar 29, 2019).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/471
Originally assigned to: @NickeManarin on GitHub.
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:
@NickeManarin commented on GitHub (Mar 29, 2019):
Nice request. :)
@zalmanlew commented on GitHub (Apr 2, 2019):
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 commented on GitHub (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.
@b-a0 commented on GitHub (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.