XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Things you’d like to miss in the future...
Post Reply
KLASS
Posts: 110
Joined: 06 Dec 2014 12:28

XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by KLASS »

Variable ?: works...
Image

admin
Site Admin
Posts: 60589
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by admin »

Works fine here.

Please describe your problem in words. I can read. :)

KLASS
Posts: 110
Joined: 06 Dec 2014 12:28

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by KLASS »

After updating XYplorer on 21.10.0025, the <xydrive> variable stopped working.
If you replace the <xydrive> variable with a variable ?:, then everything works.
The picture above shows it.

1. Create the Programs folder on disk D
2. Put the XYplorer folder (without settings) in the Programs folder
3. Also, for example, put the AkelPad folder in the Programs folder
4. Create a permanent variable
perm $prog; $prog = "<xydrive>\Programs";
6. Change the variable
$prog = D:\Programs ===> $prog = <xydrive>\Programs
6. Create a user button.
Image
7. Click this button to launch AkelPad
8. Open any disk in XYplorer and click the created Button again
Image

jupe
Posts: 2794
Joined: 20 Oct 2017 21:14
Location: Win10 22H2 120dpi

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by jupe »

It is because you are editing the variable directly through the PV menu entry and entering it unresolved, so you need to resolve it in your script, wherever you are calling it, although XY resolves it in the error message later (going by your screenshots that error msg does look to be incorrectly resolved though, but I haven't tested). The same would happen for any enviro/xy variables, not just <xydrive>, and "?:" syntax performs differently again compared to a perm var.

So this: perm $prog = "<xydrive>\Programs"; actually resolves it then stores it resolved in the PV, that is not the case when you edit it directly in the PV editor, and enter is in raw form, when you do that you need to resolve it yourself in your script.

KLASS
Posts: 110
Joined: 06 Dec 2014 12:28

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by KLASS »

jupe wrote: 01 Oct 2020 06:02 It is because you are editing the variable directly through the PV menu entry and entering it unresolved.
The above is just an example, but! I didn't touch (change) the variable. I created the variable a long time ago, and the problems started immediately after updating XYplorer to version 21.10.0025.

admin
Site Admin
Posts: 60589
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by admin »

Nothing changed here in 21.10.0025. I cannot see any problems. :|

KLASS
Posts: 110
Joined: 06 Dec 2014 12:28

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by KLASS »

admin wrote: 01 Oct 2020 11:45 Nothing changed here in 21.10.0025. I cannot see any problems. :|
Please watch this movie carefully :wink:
Image
The same movie in swf format https://yadi.sk/d/DgldHhB-D7LyPA
XYplorer21.10_and_ 21.10.0033.swf

highend
Posts: 13327
Joined: 06 Feb 2011 00:33
Location: Win Server 2022 @100%

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by highend »

On left click: open """$prog\AkelPad\AkelPad.exe"""
Try that and btw, there is a name and icon field for a ctb so there is no need to put that stuff in the script part
One of my scripts helped you out? Please donate via Paypal

KLASS
Posts: 110
Joined: 06 Dec 2014 12:28

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by KLASS »

The point is that in 21.10 works in 21.10.0033 - no :wink:

highend
Posts: 13327
Joined: 06 Feb 2011 00:33
Location: Win Server 2022 @100%

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by highend »

The point is that you try that and tell me if it works...
One of my scripts helped you out? Please donate via Paypal

KLASS
Posts: 110
Joined: 06 Dec 2014 12:28

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by KLASS »

Code: Select all

open """$prog\AkelPad\AkelPad.exe"""
This is how it works!
There may be a lot of buttons and you don't want to edit them, you want to find out why it doesn't work in 0033
It is easier to change the variable to ?:\Programs, but it was unexpected for me when all programs stopped running after updating to XYplorer 21.10.0025
Last edited by KLASS on 03 Oct 2020 23:32, edited 1 time in total.

highend
Posts: 13327
Joined: 06 Feb 2011 00:33
Location: Win Server 2022 @100%

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by highend »

It fails since v21.10.0024, so it's probably the change to open that causes this
One of my scripts helped you out? Please donate via Paypal

admin
Site Admin
Posts: 60589
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by admin »

highend wrote: 03 Oct 2020 23:28 It fails since v21.10.0024, so it's probably the change to open that causes this
What exactly fails?

highend
Posts: 13327
Joined: 06 Feb 2011 00:33
Location: Win Server 2022 @100%

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by highend »

Executing open "$prog\AkelPad\AkelPad.exe" (or any other executable)
when you have a permanent variable named $prog that has the content <xydrive>\Tools where <xydrive> is the literal string (unresolved)
and when the list pane is inside a drive (e.g. C:\). It does NOT fail if you are in "This PC"!

It does work in v21.10.0023, but not in v21.10.0024

The black screen at the end is Notepad++ started...
GIF 04.10.2020 10-42-33.gif
GIF 04.10.2020 10-42-33.gif (493.32 KiB) Viewed 1529 times
One of my scripts helped you out? Please donate via Paypal

admin
Site Admin
Posts: 60589
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: XYplorer 21.10.0025. The <xydrive> variable doesn't work.

Post by admin »

Alright, thanks! :tup: Fix is on the way.

Post Reply