mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-26 23:55:57 +03:00
[GH-ISSUE #758] Undesired Padding Around Captured Window #607
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#607
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 @dsanders11 on GitHub (Nov 15, 2020).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/758
When recording a window, the default behavior seems to add two pixels of padding around a window for the capture area. There doesn't appear to be a setting to change this behavior.
It's less than ideal behavior, since it will cause some of the background to be captured and causes a border on the recorded GIFs.
If it's intentional behavior, a setting to change which shows this padding value and lets it be changed to zero would be ideal.
@NickeManarin commented on GitHub (Nov 15, 2020):
It's there to capture a focused window. Windows with focus have a 1px border (in Windows 10).
@dsanders11 commented on GitHub (Nov 15, 2020):
Would it be possible to add a setting to change this behavior? The window I'm recording (VS Code) doesn't have a border, so it's leading to more than the window being captured.
@NickeManarin commented on GitHub (Nov 22, 2020):
Yes, it can be added as a size modifier for a VS Code instance when detecting the windows.
You can also crop the recording afterwards.
@dsanders11 commented on GitHub (Nov 23, 2020):
Is that something that currently exists, or needs to be added? Didn't find any settings for "size modifier".
I'd likely to make a lot of recordings, needing to crop them all afterwards doesn't sound very appealing. 🙂
@NickeManarin commented on GitHub (Nov 29, 2020):
In code, when detecting the size of the windows, when detecting that it's a VS Code instance, the rectangle will be reduced by 1 px.
@NickeManarin commented on GitHub (Jun 25, 2021):
Closing this ticket to focus on #915
@GiovanH commented on GitHub (Jan 24, 2022):
I came here to report this same issue. On Windows 10, there are two pixels of padding around every window, including VS and windows with custom decorators but also stock windows. I would definitely love to see a global "don't pad windows" option, as the "Window" selector is currently not really usable.