Tree/File list width, min and divider width can be handled with .Divider member. This avoids adding lots of accessor funcs unnecessarily:
I didn't know todo lists existed in markdown before this, that's cool
Yeah, only in GitHub's own brand of markdown though, unfortunately. There's a list of all the extra stuff they've added a little way down this page.
Preview for changes:
@robotboy655 Do you think this should reset the file list (on the right) when the base directory is updated or the game path is changed?
I have no idea what you are talking about.
I think it should
At present, if you change the directory from which the tree is generated, the current folder being displayed on the right does not change. This would allow a user to view a directory that doesn't exist on the tree. This isn't a problem since the tree does not follow the current folder, so it's a matter of preference.
Okay then, I'll make the changes and push it later. Cheers
How do you squash commits?
The clean way to do it involves resetting the HEAD to match the master, and then staging all the changes in your local repo again. The way I use is only a good idea if noone else has pulled down or forked your repo, as it rewrites history. You run git rebase -i HEAD~xx where xx is the number of parent commits you want to mess with. It'll bring up a text file with the number of commits you specified. You can then change the keywords on each line from pick to squash or fixup, as well as reorder them. It's risky though, so make sure you check it before you push it. You'll need to run git push -f, otherwise GitHub won't let you modify the history.
You should use the first method unless you need to reorder or delete commits.
Updates and improves DFileBrowser
Also fixes spelling in DHorizontalDivider (Rigth -> Right)