mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #10] Exception using read only file as watermark #12
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#12
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 @duarteframos on GitHub (Sep 16, 2016).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/10
Originally assigned to: @NickeManarin on GitHub.
Trying to use a read only image file as a watermark generates an exception stating the
mscorlib.WinIOError
@duarteframos commented on GitHub (Sep 17, 2016):
Just a note, the same exact file without read-only permissions works fine
@duarteframos commented on GitHub (Sep 19, 2016):
There seem to be other nasty side effects. Having previously loaded said read only file on the last session, ScreenToGif now fails to load the editor even though recording works fine.
After recording or trying to open the editor it throws this exception
The inner exception shows the same error in the report.
I'll probably have to clear my preferences before I can use it correctly again, though no serious damage so far :)
@NickeManarin commented on GitHub (Sep 19, 2016):
Oh, that's indeed a serious bug. Thank you for the detailed feedback.
You'll find the settings to delete here: C:\Users[UserName]\AppData\Local\Nicke_Manarin
@duarteframos commented on GitHub (Sep 19, 2016):
Welcome. Clearing the preferences folder worked fine, thanks again.
@NickeManarin commented on GitHub (Sep 21, 2016):
Fixed. Thank you.