XYplorer Beta Club

If you have Home set as a folder inside your User folder, My Documents folder, etc..., but you originally set it while in one of the specialty tree items (i.e. when you have XY configured to show My Documents in the root of the tree, for example)... when you execute the Go Home command, it brings you to the correct folder - but it does so in the full tree.

I think it would be helpful if XY noted whether you were in the full tree when you set the home location, or in one of the specialty folders - and respected that when you executed Go Home. Now, if you subsequently disabled that specialty folder, it should then go to the full tree, of course.

But the way it is now, I sometimes work off of the specialty tree items because the full path is particularly convoluted to get to, and it makes a mess of things unnecessarily. When I do that with the Home feature, however, I lose the ability to keep everything neat the first time I use Go Home.

Having XY consider the context would be a nice feature for people working under similar conditions. Just my two cents.

+1 cent to the ballot.

I probably did not get it right, but when I set a home to "Desktop" then Go Home brings me to Desktop (as desired), not to C:\Dokumente und Einstellungen\Donald\Desktop\.

admin wrote:I probably did not get it right, but when I set a home to "Desktop" then Go Home brings me to Desktop (as desired), not to C:\Dokumente und Einstellungen\Donald\Desktop\.

Aha! That led me to discover the issue, then!

If I set Home via the UI, it works properly. But when I set it via a script that runs "tab("sethome", $CurrentPath);", *that's* when it doesn't do it properly.

Did I not code that command properly, or is this a bug with that scripting command?

Mesh wrote:

admin wrote:I probably did not get it right, but when I set a home to "Desktop" then Go Home brings me to Desktop (as desired), not to C:\Dokumente und Einstellungen\Donald\Desktop\.

Aha! That led me to discover the issue, then!

If I set Home via the UI, it works properly. But when I set it via a script that runs "tab("sethome", $CurrentPath);", *that's* when it doesn't do it properly.

Did I not code that command properly, or is this a bug with that scripting command?

Well, where is $CurrentPath from? Its value is the one that counts...

admin wrote:
Well, where is $CurrentPath from? Its value is the one that counts...

I'm in the exact same place that we've been talking about - somewhere in the My Documents folder directly off the tree. It works fine when using the UI's Set Home command, but doesn't get set correctly when using the script command I mentioned.

Mesh wrote:

admin wrote:
Well, where is $CurrentPath from? Its value is the one that counts...

I'm in the exact same place that we've been talking about - somewhere in the My Documents folder directly off the tree. It works fine when using the UI's Set Home command, but doesn't get set correctly when using the script command I mentioned.

Show the part of the script where $CurrentPath is set.

Could it be that your script sets $CurrentFolder to <curpath> instead of <curpath_s>? According to the help file, the former does indeed return the real current path, whereas the latter returns the special current path if applicable (e.g. Desktop\New Stuff); otherwise it returns the real current path.

That was it. I was using get("Path") (or something along those lines).

I changed that to <curpath_s>, and that fixed the issue. I originally found the path under the "get" command, and didn't see anything regarding special paths, so I used what was available.

Thanks for pointing that out to me, and I apologize for the unnecessary request.