MiniTree

[jacky]

Thanks Don, 7.80.0027 does what I asked for. But like Jacky said there can be an option to enable/disable tree scroll. Because there are two kind of users here:
1) Ones who want the tree to complete freeze when auto-synch is disabled and
2) Others who want the tree scroll to get the position of current folder in tree.

I'll try to do it without adding a further option. Let's see how it works out.

Yeah, as I said, I don't like that even when I Lock Tree (using MiniTree) the Tree still scrolls when I browse elsewhere. It means using MiniTree we cannot "lock the tree", instead that option means something else, like stay in sync only for loaded nodes, but not lock the Tree, as it does with the "normal" Tree.

Which sucks, because I like to lock my Tree to go some folders do something, or have scripts go do their work on folders, without my Tree to be affected (including its scroll position), and now I can't, or I can't use MiniTree then.

[jacky]

Unrelated stuff:

- Could it be possible that when using loadtree you don't load My Computer ? I know it's technically the root of all, but I wouldn't mind having a drive as first node on the MiniTree, wouldn't look odd or anything to me, so if that's no trouble...

- Bug: You're in a folder, with a node on MiniTree. It has subnodes, but not all subfolders have been loaded, only a few (or just one even), and you have Suspend Auto-Refresh on. Turn it off, and XY loads all the subfolders on the Tree! I wish it wouldn't do that (Refresh Current Folder?), not when MiniTree is on at least.

[admin]

Thanks Don, 7.80.0027 does what I asked for. But like Jacky said there can be an option to enable/disable tree scroll. Because there are two kind of users here:
1) Ones who want the tree to complete freeze when auto-synch is disabled and
2) Others who want the tree scroll to get the position of current folder in tree.

I'll try to do it without adding a further option. Let's see how it works out.

Yeah, as I said, I don't like that even when I Lock Tree (using MiniTree) the Tree still scrolls when I browse elsewhere. It means using MiniTree we cannot "lock the tree", instead that option means something else, like stay in sync only for loaded nodes, but not lock the Tree, as it does with the "normal" Tree.

Which sucks, because I like to lock my Tree to go some folders do something, or have scripts go do their work on folders, without my Tree to be affected (including its scroll position), and now I can't, or I can't use MiniTree then.

I see.

Anybody else that dislikes the latest developments?

[admin]

Unrelated stuff:

- Could it be possible that when using loadtree you don't load My Computer ? I know it's technically the root of all, but I wouldn't mind having a drive as first node on the MiniTree, wouldn't look odd or anything to me, so if that's no trouble...

- Bug: You're in a folder, with a node on MiniTree. It has subnodes, but not all subfolders have been loaded, only a few (or just one even), and you have Suspend Auto-Refresh on. Turn it off, and XY loads all the subfolders on the Tree! I wish it wouldn't do that (Refresh Current Folder?), not when MiniTree is on at least.

1. No, the presence of a root node is necessary -- it's a hard-coded necessity, sorry.

2. Yes, I'm aware that Auto-Refresh avec Mini Tree generally needs some tuning. I wonder if Auto-Refresh should happen at all, and if yes in what form. Tricky...

[jacky]

1. No, the presence of a root node is necessary -- it's a hard-coded necessity, sorry.

2. Yes, I'm aware that Auto-Refresh avec Mini Tree generally needs some tuning. I wonder if Auto-Refresh should happen at all, and if yes in what form. Tricky...

1. No worries, was just to save a few pixels but I'm fine with it.

2. Well, there definitely should be some AR yes, I just think if should never add a node to the Tree without the user requesting it (e.g. manually doing Refresh Current Folder), to remain true to the idea of MiniTree. So XY spotting a folder creation for instance shouldn't add it to the Tree, and "un-suspending" AR shouldn't add nodes either.

[admin]

1. No, the presence of a root node is necessary -- it's a hard-coded necessity, sorry.

2. Yes, I'm aware that Auto-Refresh avec Mini Tree generally needs some tuning. I wonder if Auto-Refresh should happen at all, and if yes in what form. Tricky...

1. No worries, was just to save a few pixels but I'm fine with it.

2. Well, there definitely should be some AR yes, I just think if should never add a node to the Tree without the user requesting it (e.g. manually doing Refresh Current Folder), to remain true to the idea of MiniTree. So XY spotting a folder creation for instance shouldn't add it to the Tree, and "un-suspending" AR shouldn't add nodes either.

Yes, the tricky part is when shown nodes are renamed or removed, especially when they are the current node. So I think invalid nodes should be removed, or if possible (that might be tricky due to the weaknesses of Windows notifications) renamed.
But there are still problems: e.g. when you drag a node from one mini tree branch to another, if the rule is "remove nodes = ok, but add nodes != ok, then you would drag a node into sweet nothingness.

[jacky]

Yes, the tricky part is when shown nodes are renamed or removed, especially when they are the current node. So I think invalid nodes should be removed, or if possible (that might be tricky due to the weaknesses of Windows notifications) renamed.
But there are still problems: e.g. when you drag a node from one mini tree branch to another, if the rule is "remove nodes = ok, but add nodes != ok, then you would drag a node into sweet nothingness.

Yes, nodes should be removed or renamed just as with the usual Tree (MiniTree off), only the additions shouldn't happen.

And, correct me if I'm wrong, but that's already a normal D&D behavior : drag a tree node into a folder, the source node will be removed but the node you dropped on doesn't get automatically expanded, and the newly created folder doesn't get a (visible) node, so it's the same, isn't it?

And if you drop on a node which had at least one visible node (i.e. was expanded) then it should be visible if the source node was visible/loaded, only makes sense to preserve that node's visibility state after it's been moved, no?

[Creat]

First of all: OMG HOW AWESOME IS THSI!?!? This is the option I've been waiting for for ages, I just didn't know it, this helps me SO MUCH it's hard to put into words. And yes, of course I have some thoughts on the subject

Anybody else that dislikes the latest developments?

Yes! me! here! (... sorry )
Even though this feature is just a few days old, I already use it quite a bit, and in my case that doesn't mean that the resulting trees (isn't it nice to be able to use a plural here!) are small. If I lock the tree I do this to mainly prevent one thing: Stop the scrolling!
Mostly it means I'm woking on some folder structure, usualy copying and moving stuff around and need to copy/move something from further away into the mix. I lock the tree, go to the location (usualy via goto or using favorites and the like), drag & drop the stuff to the various folders (usualy it's more than just one target, so ctrl-c and ctrl-v won't do), click back and unlock it again.
I'm actaully fine with a node being selected if it's in the tree, as long as it doesn't scroll there, that just screws the whole locking concept for me as well. Wouldn't this acoomodate all angles (or at least more) of the problem?

Things I've noticed & Suggestions on the Subject:

• I think "minitree from current tree" (meaning: ':: loadtree ,1') should be in the Context menu of the toolbar icon. It's an intuitive and basic function I think
• Bug: Assuming I'm in folder "C:\Test" which contains folder called 'a', 'b' and 'c', if I select b and c, execute the basic 'add to mini-tree' script ( http://www.xyplorer.com/xyfc/viewtopic. ... =15#p28773 ), the focus moves to folder b (and I didn't say go anywhere). This makes the [:: loadtree $xyz,1] equivalent to pressing [enter] if just one item is selected.
• Bug: executing ":: loadtree ,1" causes the focus to be set to "My Computer", regardless of current folder it seems.
• Request: how about the Mini-Tree management option of removing items from the tree with "loadtree"? For example using "loadtree $list, 2" to remove the items in that list (if they are part of the tree). This shouldn't be much effort to add it and make me SOOO happy
• Currently I can't graphically remove nodes from the tree (afaik) except with something that seems to be a side effect (or has a side effect, semantics ). If you shift-click a [-] in the tree all subnodes are removed fromthe mini-tree, so continuing the example with "C:\Test" from above would mean shift-clicking the [-] of Test and then entering folder 'a' via doubleclick in the list means only folder a is shown. This is GREAT! Unfortunately the shift-click also opens a new tab
• The next one got a bit long, so it's the rest of this entry below

I think I have to explain this next one a bit further, it's also a bit complicated I'm afraid. I primarily use the tree to navigate wherever I want to go, I barely ever doubleclick in the list. So I'd love to have a way of using that with the Mini-Tree (this also has practical applications besides my habits). Since ALT is currently unused in the tree (shift opens in a new tab, ctrl in a background tab) how about having alt-click remove all other siblings from the Mini-Tree?
Example: assume I'm in the "C:\Test" from above, siblings weren't added in any way. Clicking [+] on the Folder adds all siblings, alt-clicking on a could enter folder a and remove b and c. This was navigating the tree would still be possible without having it clutter the Mini-Tree.
And yes, there's more: it would be even better (not to mention MINDBLOWINGLY GREAT) if there was a possible temporary 'only-for-one-click' state (making the above idea superfluous again). I'm gonna have a really hard time explaining this coherently so please bare with me.
Assume you have a folder with a lot of subfolders (like a big MP3 collection with one folder per album or something) and you can navigate around among them while using the tree, but only visited folders are actually added. Assume you have maybe 10 or so folders (albums in our example) visible (meaning part of the minitree). You alt-click the parent (mp3-folder), now all subfolder (albums) are displayed, BUT those not part of the minitree appear lighter (as if they were cut with ctrl-x for example) and only temporarily, as whatever action you take next in the tree hides them again.
This would allow a multitude of things like moving to a still-hidden folder via tree (currently not at all possible if children of that node are already shown since it completely expands it) or copy/move already selected files from the current folder to a still-hidden folder without showing it at all (alt-click shows all those folders temporarily, drag&drop on the tree is the next action there so it hides them again, but since the node was interacted with one could argue it might be a good idea to add it in that case). This temporarily showing the nodes could also happen when you hover the mouse over an only partially visible folder while drag&dropping files (hovering for more tha 2 seconds or so). This would have endless posibilities!

Thoughts on my thoughts? Comments? Better ideas?

Keep up the great work, what an awesome idea (and yet it even still has so much potential)!
Creat

[admin]

Ah, I love it when ideas are thrown at me in form of long brain-stormy lists! Yeah, give to me!

Allow me to pick out some points:
- Stop the scrolling! Okay, okay, got the message, will do.
- Minitree from current tree: yep, goody, will do.
- Shift+[-]: HA! I totally forgot that feature, thanks! But it works nicely here, does not open a new tab. Explain again. BTW, I will add an item "Hide (current folder) from Mini Tree" to the ctx menu. Selection will move to the parent folder.

[*]Bug: Assuming I'm in folder "C:\Test" which contains folder called 'a', 'b' and 'c', if I select b and c, execute the basic 'add to mini-tree' script ( http://www.xyplorer.com/xyfc/viewtopic. ... =15#p28773 ), the focus moves to folder b (and I didn't say go anywhere). This makes the [:: loadtree $xyz,1] equivalent to pressing [enter] if just one item is selected.
[*]Bug: executing ":: loadtree ,1" causes the focus to be set to "My Computer", regardless of current folder it seems.
[*]Request: how about the Mini-Tree management option of removing items from the tree with "loadtree"? For example using "loadtree $list, 2" to remove the items in that list (if they are part of the tree). This shouldn't be much effort to add it and make me SOOO happy

Bug 1: the first folder in loadtree is set to be the current folder. It might be an idea to make that optional somehow (= do not set a new current folder).

Bug 2: I'll check that...

Request: I had the same idea already... will see...

Enough for now. Doing the stuff is a bit harder than talking about it... Keep your other ideas in the fridge and serve them later.

[admin]

"Mini Tree from Current Tree" ... any other suggestions for this caption? It's a little long...

[Creat]

- Minitree from current tree: yep, goody, will do. ... any other suggestions for this caption? It's a little long...

"Convert to Minitree" maybe, but it's not that much shorter (should obviously be greyed out if minitree is already active). Ah or how about "Use as Minitree" or something?

- Shift+[-]: HA! I totally forgot that feature, thanks! But it works nicely here, does not open a new tab. Explain again. BTW, I will add an item "Hide (current folder) from Mini Tree" to the ctx menu. Selection will move to the parent folder.

Ok to be more specific, it only opens a new tab when clicking the [-] of the current folders parent it seems (had to play around a bit to reproduce it, started to question my sanity ). so if c:\test\a is active and you shift-click the [-] of test.

Bug 1: the first folder in loadtree is set to be the current folder. It might be an idea to make that optional somehow (= do not set a new current folder).
Bug 2: I'll check that...

Actually the reply to Bug 1 (almost) explains Bug 2. The behaviour makes some sense if you actually load a tree, since it's gonna replace the new tree (might be nice to check at least if the current folder is part of it and not change it in that case, or move up the tree until a parent is). But if you only add something to the tree the current folder has to be still part of the tree (excluding a locked tree, but that situation is a bit special anyway). Having it as an option works too of course

Request: I had the same idea already... will see...

Awesome, I guess (meaning hope) that means it's gonna happen (at least at some point)! Nice!

bye
Creat

[admin]

- Shift+[-]: HA! I totally forgot that feature, thanks! But it works nicely here, does not open a new tab. Explain again. BTW, I will add an item "Hide (current folder) from Mini Tree" to the ctx menu. Selection will move to the parent folder.

Ok to be more specific, it only opens a new tab when clicking the [-] of the current folders parent it seems (had to play around a bit to reproduce it, started to question my sanity ). so if c:\test\a is active and you shift-click the [-] of test.

Ah yes, this cannot be changed. Browsing to a new location (which will happen due to this action) while SHIFT is down will open a new tab. No way out.

[Creat]

Damn, that's very unfotunate... I usualy don't use tabs that much and was kinda baffled to see I suddenly had 8 or so... So I guess I often shift-close folders where I'm in a child. Ah well, will have to get used to move up by hand first I guess.

[admin]

Damn, that's very unfotunate... I usualy don't use tabs that much and was kinda baffled to see I suddenly had 8 or so... So I guess I often shift-close folders where I'm in a child. Ah well, will have to get used to move up by hand first I guess.

A solution would be to change the functionality from SHIFT to CTRL. I don't see a problem here...

[Creat]

Yes that would be quite nice!

And, I know you've mentioned that you know there are issues with file system refreshes, and just in case you don't know this yet I'll just list it here:
Using my example from above, if you have The folder c:\test and it shows only one child (say folder a), and you copy/move a file to or from c:\test it will be refreshed and show all children (a, b and c).

I also noticed that it might be nice to have a visual hint that a folder currently only shows part of the subfolders (similar to the third [grey] state of a checkbox) and incorporate that somehow. Currently there doesn't seem to be a direct way to show all children of a partially expanded node. You can shift-close it and expand it again (which currently shows all children) but this also closes/resets all those child nodes down the tree (if folder a from the example was the only one shown below test and had 2 children '1' and '2', where only 2 was shown, this would afterwards show a closed a).

Sorry for all the long explanations, I tend to be a bit ober-precise
Creat