Show '..' (parent) in folder

[admin]

RSI: yep, been there from too much hi-hat action on the drums. I couldn't hold a beer bottle for 6 months with my right hand.

[admin]

This sounds good. I have no clue how it will work then, but i will see.
Many thanks for your commitment.
I think it was a good idea to switch from SpeedCommander. The XY offers so much more and i like the community.

You just add an item to the Catalog and put .. in to the Location field.

2022-05-05_125447.png (10.14 KiB) Viewed 1889 times

Then you have this thing to click on for "go up" (and you don't even have to scroll up the list):

2022-05-05_125501.png (4.77 KiB) Viewed 1889 times

[raraz]

Hi,
Not sure if its me but
"tweak ABRelativeToAppPath is set to 1." doesnt seem to work. Both 0 or 1 go to application path.
I did restart the app.

[admin]

You need v23.00.0207 or later.

[omid]

Additionally from the next beta onwards you can use .. as location in a Catalog item to go upwards from here:

Code: Select all

    * Catalog: A location ".." was by default resolved relative to app path. Nobody needs 
      this. Now it is resolved relative to the current path.
      Exception: tweak ABRelativeToAppPath is set to 1.

Hi Don
Are you planning to change the behavior of this function as well?
resolvepath("..")

I use it a lot to find the parent folder of XYPlorer because of my folders structure.
.../portable/
.../portable/xyplorer
.../portable/mpv
.../portable/others

For example, in CFA:

Code: Select all

|"MVP|MPV.ico" {:Video}>::run resolvepath("..")."\MPV\mpv.exe --config-dir=".resolvepath("..")."\MPV\mvp ""<curitem>""" ;

Can you please add a native variable like <xyparent> equal to resolvepath("..")

[admin]

No, resolvepath("..") has not and will not be changed. So there is no need for <xyparent>. Right?

[highend]

A bit shorter and easier to read...

Code: Select all

|"MVP|MPV.ico" {:Video}>::$p = resolvepath(".."); run lax("$p\MPV\mpv.exe" --config-dir="$p\MPV\mvp" "<curitem>");

[omid]

No, resolvepath("..") has not and will not be changed. So there is no need for <xyparent>. Right?

It would be helpful if there was a <xyparent>, because it makes the code shorter and more understandable.

[omid]

A bit shorter and easier to read...

Code: Select all

|"MVP|MPV.ico" {:Video}>::$p = resolvepath(".."); run lax("$p\MPV\mpv.exe" --config-dir="$p\MPV\mvp" "<curitem>");

Thank you highend, as always, I learn a lot from your codes

[highend]

If think <xyparent> makes total sense. Especially for all the people that store XY in a portable folder (and belonging tools one level above)....

[WirlyWirly]

I use

<xypath>..\..\

when accessing the parent folder where I keep XY. It works fine, but if I could make it more readable with <xyparent> then I'm all for it.

One of the selling points on the XY homepage is portability, so having such a variable would be beneficial for the users who use relative paths in order to maintain that portability.

You can never have enough environment variables. Useful for people who need them and unobtrusive for those that don't. Win-win.

[admin]

You should use <xypath>\.. to go to the parent folder. Your pattern leads to an invalid path that leads to the right goal only through grace.

I'll add <xyparent>.

[omid]

Thank you for adding <xyparent>

[jupe]

(with my mouse).

2022-05-07_104729.png (5.04 KiB) Viewed 1674 times