mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #561] Uncap negative border maximum #458
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#458
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 @DanielRosenwasser on GitHub (Nov 24, 2019).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/561
Originally assigned to: @NickeManarin on GitHub.
I want to create room above an existing GIF so that I can put a static image on every frame via the watermark feature. Recently, you added the ability to expand borders in a negative direction (#313) which is great! However, setting a negative border is capped to -20. I need much more room there.
Any chance this can be uncapped? Or is there a better way to only change the canvas size without scaling existing image frames?
@DanielRosenwasser commented on GitHub (Nov 24, 2019):
(I guess what I'm really looking for is a way to change canvas size, and "add border" is my roundabout way of asking for it)
@NickeManarin commented on GitHub (Dec 4, 2019):
I'm going to increase the limit, but in a future version, I'll add the option to resize the canvas too.
@NickeManarin commented on GitHub (Dec 5, 2019):
https://github.com/NickeManarin/ScreenToGif/issues/551
I decreased the limit to -500, is that enough?
@DanielRosenwasser commented on GitHub (Feb 23, 2020):
Sorry for not following up - yes, that's probably reasonable for what I was trying to do. Thanks!