It might be because the extra information is shown if it has already been read by tree. e.g. If you manually expand a tree branch (or if the "expand selected" option expanded the branch, or if it was auto-expanded before "no content population" was selected), then that branch will always be fully expanded if it is expanded at all.
(The intent of the "no content population" is to avoid reading the folders on very slow drives, so it still shows them if it already has them. That it also lets you have a tree with minimal extra folders is more of a side-effect.)
That will turn the tree off and then immediately back on, causing it to forget any cached information and re-build itself with just the direct path to your current location. Essentially, it is a "clear extra folders from tree" button, as long as "no content population" is on.
I think, there's still something wrong with tree and the expand functionality, maybe, lnh, that's what irritated you a bit.
For network drives e.g.: Open a a location within your lan (UNC) and toggle the tree to open, the unc-folder will be expanded in the tree, even though the settings are set to "populate contents for local devices only". Now switch from source to dest an back and that network location folder in the tree will be collapsed. Toggling the tree expands it again, which I think is odd.
On the other hand: I have also selected "Expand selected branch" and the currently selected local folder I have opened in source or dest does not expand, which I find odd as well. (Look here: Tree "expand selected branch" not applied on focus changeTree-View item out of view) which is aehm.. I mean I have no explanation! o)
If you expand a branch manually by clicking the + it will always expand fully; the "populate" options only apply to branches that are expanded automatically through navigation.
"expand selected branch" applies when a branch is newly selected (including when the tree is first opened), but not if you collapse the branch yourself and then toggle twice between source and destination sides. I think that explains everything you are seeing.
I just have "expand selected branch" enabled and branches will not expand when switching between source/dest, only when navigating up/down in the filedisplay. Additionally: Manually expanding the current folder in the tree will result in collapsed state after switching source/dest. I don't know for sure, but this does not feel right to me.
Did you look at "the other thread" I linked several times? I'll link that image right here again:
To me that "Collections" folder looks selected, but maybe there is a misunderstanding going on?!
Leo, I did not collapse a branch myself, I just toggled between source and dest. Is that equal to collapsing the current branch? I guess it's not. Am I wrong? I'd really appreciate a hint on where my fault is, as I keep on thinking that the tree misbehaves. Don't know how others feel about it, but I expect the tree to be able to appear expanded for whatever folder I currently work with. Wether I just opened the tree, used Go parent/ or switched between source/dest shouldn't make a difference as long as "expand selected branch" is enabled.(?) Thanks for your patience and looking forward to a non-quoted response! o))
So I tried to enable/disable some other settings in prefs -> tree -> options, just to see if I could get expected behaviour with some different setup, unfortunately that didn't work out.
So, without your input on how this should work and without any hints on what I might be doing wrong, this still looks like some kind of malfunction from my perspective. I cannot have an expanded tree after toggling focus between source/dest in a dual lister, even though "expand selected branch" is enabled.
I'm actually a bit surprised that you don't seem to care. I got the impression at least, but maybe time is just too short on your side currently or my help-credits reached zero, don't know. o) See you soon, in another thread! o)
The "expand selected branch" option does not affect implicit tree selection changes that happen by toggling source/dest sides. We could change that, but that's how it works right now.
That behaviour may be unexpected but once it's known I think everything you're seeing makes sense, along with the other tree options in play.
I felt your previous statements always included an assumption or pre-condition that was not true for me, so I chose to stay and ask again to make sure, but anyway, this last response is very clear and we finally made it through! o) Thanks for your patience. o)
