mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #23] Argument exception when using relative paths #24
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#24
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 (Oct 2, 2016).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/23
Originally assigned to: @NickeManarin on GitHub.
Here I am again, sorry to bother again so soon
Using a relative path in the save path dialog generates an exception only when pressing the Choose the Location button, even though regular saving works just fine.
PresentationFramework.GetShellItemForPath
Now I know this is probably unorthodox, and most likely not a foreseen use, but I'dd politely ask you if possible to fix the bug without removing the relative path support :)
I love using applications with a as portable as possible environment, because some times I am away from my computer running from portable HDD or Thumbdrives, and relative paths are very handy. Also a friendly reminder to eventually bring back true portable mode, including saving preferences in the application folder ;)
@NickeManarin commented on GitHub (Oct 6, 2016):
Fixed, thank you. :D
Also, if it's a relative path before opening the "Choose folder" dialog, it will return a relative path too.
@duarteframos commented on GitHub (Oct 6, 2016):
Yay thanks for the fix. Also great to know relative paths are kept, great step towards portability! :D