mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #59] Override set to frame 0 does not have an effect #1424
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#1424
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 @igor2x on GitHub (Jan 13, 2017).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/59
Problem on ScreenToGif 2.4, but it was already a problem in previous version 2.3.2.
Somehow work-around:
It looks to me time for first frame (frame 0) is set it is just skipped.
@NickeManarin commented on GitHub (Jan 13, 2017):
Do you mean during the preview (playback)? The override sets the value to 5000ms, but the preview jumps right away to the next frame while starting the playback.
@igor2x commented on GitHub (Jan 13, 2017):
Exactly in step 3 overrride was set to 5 seconds, but playback (the same if saving into gif file) just jumps right away to the next frame.
Frame 0 is the only frame having this problem. Is there maybe something related to numbering the frames, you know first frame has a name 0?
@NickeManarin commented on GitHub (Feb 6, 2017):
There was a bug with that field (the override box) not being able to update the value to override the selected frames. Only after the second time it was updating the value.