fix broken context menu "open file location"#21
Open
crmbz0r wants to merge 1 commit intoasdf31jsa:fusionfrom
Open
fix broken context menu "open file location"#21crmbz0r wants to merge 1 commit intoasdf31jsa:fusionfrom
crmbz0r wants to merge 1 commit intoasdf31jsa:fusionfrom
Conversation
After an user reported the issue in discord, I noticed some weird behavior too when using a portable version and trying to use "open file location" on an source image, where it kept sending me to my user documents folder and not the actual file location. Target video location seems to be fine, but I just applied the same fix for both because it's a robust solution and now opens the file locations reliably for both.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After an user reported the issue in discord, I noticed some weird behavior too when using a portable version and trying to use "open file location" on an source image, where it kept sending me to my user documents folder and not the actual file location. Target video location seems to be fine, but I just applied the same fix for both because it's a robust solution and now opens the file locations reliably for both.