mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 23:25:52 +03:00
[GH-ISSUE #287] Import a GifFile without normal file ending #237
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#237
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 @EndlessMISAKA on GitHub (Mar 13, 2018).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/287
Originally assigned to: @NickeManarin on GitHub.
When a GifFile is not end with a GIF Trailer, that the Program will getting into a no-end loading.
Since we used the same Decoder, so I used the bad giffile to tested, and found this bug.
In my program this bug will throw a exception, so I changed the code to ignore the exception.
Maybe you will has a question that why should I need to fixed this bug?
Because this bad giffile can open by Windows Photo like a normal giffile.
Best Wishes to you.This is a wonderful program.
(Sorry,I don't good at English.)
@vatterspun commented on GitHub (Mar 16, 2018):
I'm not sure I understand what you're having issues with.
Could you describe what you saw? Could you then describe what went wrong? What were you expecting to see?
@NickeManarin commented on GitHub (Mar 16, 2018):
@vatterspun The app stays in an infinite loading process when a corrupted gif file is imported. So, @EndlessMISAKA wants the app to be able to load all possible frames, without staying in an infinite loading.
@NickeManarin commented on GitHub (Mar 16, 2018):
Done. With v2.13, it will load all frames until it can read anymore.