Another script bombing out in ver 17

[Kucera]

After update from 15 something to 17.04.01, the over 2 years old script calling BeyondCompare says
"BCompare.exe not found.
Edit script and check path"
Here's the path to it:
"C:\Portables\Beyond Compare 3\BCompare.exe"
and attached is the script - I made sure the path is the same in there, so does the new version of XY need something else in the script?
Thanks for any help.
Regards Emil

[highend]

Show a screenshot from the folder that contains the .exe file. I want to see the
address bar in that picture as well as the .exe scrolled into a visible position

[Kucera]

Show a screenshot from the folder that contains the .exe file. I want to see the
address bar in that picture as well as the .exe scrolled into a visible position

Here it is; should be correct, I copied the path right form XY …
Regards Emil

[highend]

Ok, so show me how you invoke this script exactly. From a toolbar, UDC, PFA... Show a screenshot that contains the call to this script

[Kucera]

Ok, so show me how you invoke this script exactly. From a toolbar, UDC, PFA... Show a screenshot that contains the call to this script

With 2 files highlighted, I use the menu Scripting-Load script file, then double-click the BCompare2.xys file. Never bothered to make a button, it does not get used all that often.
regards Emil

[highend]

I don't see the call to the script file through that description but regardless.
Edit the script.

Code: Select all

end (exists("C:\Portables\Beyond Compare 3\BCompare.exe")=="0"), "BCompare.exe not found.<crlf>Edit script and check path.";

Place a question mark right in front of the "end" like this:

Code: Select all

?end (exists("C:\Portables\Beyond Compare 3\BCompare.exe")=="0"), "BCompare.exe not found.<crlf>Edit script and check path.";

Save it, invoke it again.

You should get a "Stepping through a script" window popping up. Click on time on "Continue" and then make a screenshot from it

[Kucera]

I don't see the call to the script file through that description but regardless.
Edit the script.

Code: Select all

end (exists("C:\Portables\Beyond Compare 3\BCompare.exe")=="0"), "BCompare.exe not found.<crlf>Edit script and check path.";

Place a question mark right in front of the "end" like this:

Code: Select all

?end (exists("C:\Portables\Beyond Compare 3\BCompare.exe")=="0"), "BCompare.exe not found.<crlf>Edit script and check path.";

Save it, invoke it again.

You should get a "Stepping through a script" window popping up. Click on time on "Continue" and then make a screenshot from it

Hello again,
I followed the instructions, edited, then, when I tried to invoke it as before, by double clicking the xys file, I got the same message, that it could not find the exe file. So I copied the script into the Scripting-Run script window, hit ok, got

1.png

clicked Continue, got

2.png

clicked Continue again, despite the message, and the BeyondCompare window opened, with the two files!
So, what was wrong? and how to invoke it now, to avoid the error msg and not have to step through the script?
Thanks for your help!

Edit:
Removing the questionmark and copying the script into the UDC seems to do the trick - invoking it now from the menu
User-Run script.
Thanks again very much
Regards Emil

[highend]

The script file you are invoking with the "Scripting-Load script file" method is NOT the one you posted here / nor the one you've just edited. That's your problem. And because I've assumed that I wanted to see the call to the script file

[Kucera]

The script file you are invoking with the "Scripting-Load script file" method is NOT the one you posted here / nor the one you've just edited. That's your problem. And because I've assumed that I wanted to see the call to the script file

By gum, embarrassed again - but now, where can I find (what directory) that file that actually works now?

[highend]

You attached the working file to your first posting?

To fix the non-working one:
Put
goto <xyscripts>;
in the address bar and hit enter

Select the file "BCompare2.xys"

Compare it to the one you attached in your first post. You probably only need to adapt the path to BCompare.exe

[Kucera]

You probably only need to adapt the path to BCompare.exe

Done, all's well now, I knew that it would not be XY that's at fault, just did not believe myself that scatterbrained, sigh …
Thanks again, very much
Regards Emil