Fix corrupted 'path' variable when going up a folder level #30
Conversation
This file contains 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
…ently it was just putting a null after the last "/" character which is fine for string functions accessing it, but the "open folder" FujiNet function looks for text after the null, and there is something it uses it as a filter. So when devancing folders, extraneous text after the null was though to be a filter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When devancing/going back/up a folder level, the "path" variable wasn't getting fully "nulled out" - it was just getting a null put in the string at the end of the new path, but the text from the previous path was still present in the string after the null. The FujiNet interprets text after the null as a "filter" for the open directory function.