feat: file browser #18
Open
Conversation
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
…y simple top bar. Removes file browser implementation, but will commit with a working change
chore: linter main and file-browser
Andy34G7
force-pushed
the
feat/file-browser
branch
from
120bf73 to
e9739d7
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Which issue(s) does this PR address?
There exists no file browser in the current implementation.
Why do we need this PR?
To access the files to import textures, etc.
What logical changes are present in this PR?
Added a new header and cpp file with the file browser, and main now has lines to initialise the same
How did you test the changes in this PR?
(Include screenshots, CLI output, etc.)
By running it and resizing multiple times.
Are there any breaking changes in this PR?
Yes. Addition of new files and changes to main.cpp
Is there some additional work to be done later that is NOT covered in this PR?
Clicking on a file doesn't do anything. Function to deal with opening files is to be implemented. file browser needs to have a tree structure and a root directory instead of the current free one.