starred/ScreenToGif

Fork 0

mirror of https://github.com/NickeManarin/ScreenToGif.git synced 2026-04-25 23:25:52 +03:00

[GH-ISSUE #555] Allow Undo Buffer Disable #456

New issue

Closed

opened 2026-02-26 09:31:29 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 09:31:29 +03:00

Owner

Originally created by @Crispin-at-Linknode on GitHub (Nov 18, 2019).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/555

Originally assigned to: @NickeManarin on GitHub.

Hi,

With large volumes of data I found that the auto-undo folder was leaving me out of disk space, for example with 4,000 images, removing 3,000 nearly doubled the space required temporarily.

Could a disk space calculation for undo be estimated, or I'd be happy with an option to make an informed decision to disable undo. perhaps on a per-session basis so it resets each time.

Many thanks - Crispin

Originally created by @Crispin-at-Linknode on GitHub (Nov 18, 2019). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/555 Originally assigned to: @NickeManarin on GitHub. Hi, With large volumes of data I found that the auto-undo folder was leaving me out of disk space, for example with 4,000 images, removing 3,000 nearly doubled the space required temporarily. Could a disk space calculation for undo be estimated, or I'd be happy with an option to make an informed decision to disable undo. perhaps on a per-session basis so it resets each time. Many thanks - Crispin

kerem

2026-02-26 09:31:29 +03:00

closed this issue
added the
🔷Enhancement
label

kerem commented

2026-02-26 09:31:29 +03:00

Author

Owner

@NickeManarin commented on GitHub (Apr 3, 2020):

Would a undo/redo limit help you?
For example:

Keep only the last N actions stored.

@NickeManarin commented on GitHub (Apr 3, 2020): Would a undo/redo limit help you? For example: - Keep only the last N actions stored.

kerem commented

2026-02-26 09:31:29 +03:00

Author

Owner

@Crispin-at-Linknode commented on GitHub (Apr 4, 2020):

Yes... as long as the limit could be set to zero!

With the example above, it is just a single operation to remove duplicates. Would a limit be on the operation or the images saved in the undo folder?
I wouldn't really want to undo to a partial state if only half the images were restored on undo.

@Crispin-at-Linknode commented on GitHub (Apr 4, 2020): Yes... as long as the limit could be set to zero! With the example above, it is just a single operation to remove duplicates. Would a limit be on the operation or the images saved in the undo folder? I wouldn't really want to undo to a partial state if only half the images were restored on undo.

kerem commented

2026-02-26 09:31:29 +03:00

Author

Owner

@NickeManarin commented on GitHub (Apr 4, 2020):

If the limit is set to zero:

The app does not save any state and you can't undo/reset anything.
All actions are permanent.

Now, if the limit is set for example, to 2:

You delete a frame: Before deleting the frame, it's stored in the action stack (pile of actions that can be undone).
You add a text on a frame: Before adding the text, the frame is stored in the action stack.
You crop the animation: Before cropping, the whole project is saved in the action stack, since all previous frames are going to be altered. After saving the state, the first action (oldest one) is removed from the stack and its files are deleted.
If you try to undo all actions (by clicking Undo multiple times or by clicking on Reset), you'll be able to undo until reaching the "text on a frame" action. So, you won't be able to recover the deleted frame.

@NickeManarin commented on GitHub (Apr 4, 2020): If the limit is set to zero: - The app does not save any state and you can't undo/reset anything. - All actions are permanent. Now, if the limit is set for example, to 2: - You delete a frame: Before deleting the frame, it's stored in the action stack (pile of actions that can be undone). - You add a text on a frame: Before adding the text, the frame is stored in the action stack. - You crop the animation: Before cropping, the whole project is saved in the action stack, since all previous frames are going to be altered. **After saving the state, the first action (oldest one) is removed from the stack and its files are deleted.** - If you try to undo all actions (by clicking Undo multiple times or by clicking on Reset), you'll be able to undo until reaching the "text on a frame" action. So, you won't be able to recover the deleted frame.

kerem commented

2026-02-26 09:31:29 +03:00

Author

Owner

@NickeManarin commented on GitHub (Apr 5, 2020):

Closing this as done.

@NickeManarin commented on GitHub (Apr 5, 2020): Closing this as done.

kerem referenced this issue

2026-03-01 18:47:58 +03:00

[GH-ISSUE #456] Feature Request: Add progress bar for Remove duplicate frames #1745

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ScreenToGif#456

No description provided.

Rows
Columns