Lost "Create Shortcut Here"in drag n drop context menu.

[admin]

That last one puzzled me because if I un-clicked the minitree button, it would go to full tree but clicking the minitree button again would always show only the current selected folder and my intuition told me (erroneously I guess) that it should go back to the mini tree I took pains to create. Oh well, however it works the problem is solved with a keystroke now.

That's an interesting comment which I had expected to hear much earlier. I was thinking about this several times when making the decisions and the current solution made it only by 51% over 49% against what your intuition told you.

And I share your intuition, so here's a little informal poll: Should the minitree button (command) rather reload the last used minitree?? I'd say YES!

[Pagat]

And I share your intuition, so here's a little informal poll: Should the minitree button (command) rather reload the last used minitree?? I'd say YES!

YES from me as well. I was also "puzzled" to loose my MiniTree the first time i switched it off temporarily. But since i saved the most-needed MiniTrees thanks to jackys script it was not that big of a deal.

But if you change the toolbar button behaviour (to show the last used MiniTree) it would save me one extra-step

[admin]

And I share your intuition, so here's a little informal poll: Should the minitree button (command) rather reload the last used minitree?? I'd say YES!

YES from me as well. I was also "puzzled" to loose my MiniTree the first time i switched it off temporarily. But since i saved the most-needed MiniTrees thanks to jackys script it was not that big of a deal.

But if you change the toolbar button behaviour (to show the last used MiniTree) it would save me one extra-step

Question: You are in MaxiTree on a location that is NOT part of your last MiniTree. When you now click the MiniTree button, shall the current location be retained and therefore added to the last MiniTree (and saved with it the next time), or shall the current location be changed to that of the last MiniTree?

[jacky]

Question: You are in MaxiTree on a location that is NOT part of your last MiniTree. When you now click the MiniTree button, shall the current location be retained and therefore added to the last MiniTree (and saved with it the next time), or shall the current location be changed to that of the last MiniTree?

I would say the later, the button would basically now defaults to "Load Last Mini Tree", no?

[admin]

Question: You are in MaxiTree on a location that is NOT part of your last MiniTree. When you now click the MiniTree button, shall the current location be retained and therefore added to the last MiniTree (and saved with it the next time), or shall the current location be changed to that of the last MiniTree?

I would say the later, the button would basically now defaults to "Load Last Mini Tree", no?

The button would toggle between Last MT and MaxiT. I wonder if browsing away from the current location is okay... well, a simple Alt+Left will bring you back there, but still...

[Pagat]

since i only use unlocked MiniTrees i'd expect that my current location would be added to the last MiniTree when switching back from MaxiTree and therefore my location would not change.

[admin]

since i only use unlocked MiniTrees i'd expect that my current location would be added to the last MiniTree when switching back from MaxiTree and therefore my location would not change.

Okay. As you see I have just uploaded a test version that goes the other way. Let's wait for some more feedback.

[yarsnave]

I vote for Load Last MiniTree. I rarely have to go to the Windows folder (amongst several others) but even though it is occasionally necessary, I wouldn't want it added to my preferred MiniTree automatically.
Optionally, perhaps a menu option, toolbar button or folder context menu item could be added in the MaxiTree to specifically add a rarely visited folder to the MiniTree.

[admin]

I vote for Load Last MiniTree. I rarely have to go to the Windows folder (amongst several others) but even though it is occasionally necessary, I wouldn't want it added to my preferred MiniTree automatically.
Optionally, perhaps a menu option, toolbar button or folder context menu item could be added in the MaxiTree to specifically add a rarely visited folder to the MiniTree.

Given that the command "Load Last Mini Tree" is still available anyway, I think now that the command "Mini Tree" should not lead to a change in location, and consequently the current path should be added to the last Mini Tree if it's no part of it anyway.

[Pagat]

Sounds reasonable. Tomorow, when i'm back at work, I'll see how this new behaviour blends in with my workstyle (I'll also check out that new MiniTree tweak )

btw.: will there be an option in the context menu to start a "new" MiniTree with the current directory (the old behaviour of the button)?

[yarsnave]

I vote for Load Last MiniTree. I rarely have to go to the Windows folder (amongst several others) but even though it is occasionally necessary, I wouldn't want it added to my preferred MiniTree automatically.
Optionally, perhaps a menu option, toolbar button or folder context menu item could be added in the MaxiTree to specifically add a rarely visited folder to the MiniTree.

Given that the command "Load Last Mini Tree" is still available anyway, I think now that the command "Mini Tree" should not lead to a change in location, and consequently the current path should be added to the last Mini Tree if it's no part of it anyway.

Yes, there's a Load Last MiniTree on the MT button context menu and that works as expected so long as you do not shut down XY and restart it. In that case, the best I can tell, my crafted MiniTree is not saved and must be re-created. That was not what I expected when I started using the MiniTree and that's why I created the UDC script to load the MiniTree I use almost exclusively.

Sorry that I didn't define what I really meant but now that I can reload my personal MiniTree on XY start-up with a keyboard shortcut, I'm great with whatever the community feels is best for all users and how they might use the MiniTree. Truth to tell, that's probably the best for me too since I'm pretty new to the finer points of XY. And I do mean FINE!

[admin]

Yes, there's a Load Last MiniTree on the MT button context menu and that works as expected so long as you do not shut down XY and restart it. In that case, the best I can tell, my crafted MiniTree is not saved and must be re-created. That was not what I expected when I started using the MiniTree...

You mean when you close XY in MaxiTree state then last MiniTree is not saved and restored? Indeed true, and now I think this should be changed! The last MiniTree should always be saved, also when not visible on shut down.

[admin]

btw.: will there be an option in the context menu to start a "new" MiniTree with the current directory (the old behaviour of the button)?

I think yes, I'll call it "Minimize Tree".

You can also do it with this script line:

Code: Select all

loadtree;

[yarsnave]

Yes, there's a Load Last MiniTree on the MT button context menu and that works as expected so long as you do not shut down XY and restart it. In that case, the best I can tell, my crafted MiniTree is not saved and must be re-created. That was not what I expected when I started using the MiniTree...

You mean when you close XY in MaxiTree state then last MiniTree is not saved and restored? Indeed true, and now I think this should be changed! The last MiniTree should always be saved, also when not visible on shut down.

Yes, that's what I meant and it was very confusing because I could also lose my MiniTree if I toggled the MiniTree button a few times without loading the last MiniTree each time I toggled.
I almost always use less than half the folders in the MaxiTree and those are in my MiniTree so it never occurred to me to do anything other than swap back to Maxi if I needed to access another folder(s) temporarily and then swap back to my Mini expecting it to be there. So I'd toggle that way a couple of times with no Mini reload and away went my Mini.
I guess my perception was that a specific Mini would fulfill all my needs and so far it has because I have not had to do any swapping of files or such between the folders in a Mini and a Maxi tree. But if I do.... Well, that's a whole 'nother ball of wax. Perhaps one that would alter the way I think about the MiniTree.