XYplorer Beta Club

The following script producers an error with the latest version of XY (15.00.0400)

"New Folder (Ctrl+N)";#231;

I tried #139 with the same results

And which error is that?

Tried it with v15.00.0400 and v15.00.0401, works fine...

Try this btw while ^that^ works, this is syntactically cleaner

Your suggestion to remove the semicolon (;) did not work. Still the same error.

The error is: 'new' is not a script command.

Works fine in 15.00.0300, so I regressed to the previous version.

BTW is there a way to include an image of the error in this forum? I could't figure out how to include an image of the error message.

Your script works fine here. No error.

How do you call the script?

I am sorry, I think I gave you the wrong info.

I have the script assigned to a toolbar button.
The failing script is the left button, not the right. See below:

on left click:
$name = input("Enter Folder Name to be created in... ", "<curpath>\", "New Folder");
end ($name == "" || $name == " " ), "No name entered!";
new ("$name", dir);

on right click:
"New Folder (Ctrl+N)" #231;

Highend, Is the above script a emplacement?

Did the script rules change?

Will XY be "fixed", or do I have to change the script?

For now, I am sticking with 15.00.0300.

Highend, Is the above script a emplacement?

A replacement? Yeah...

Did the script rules change?

Why?

You've used new (...
but it's new(...
Hence the error.

Will XY be "fixed", or do I have to change the script?

No clue what you mean.

My old script worked for a few years, in XY.
Something changed in 15.00.0400.
15.00.0300 still works, using the original script.

My question was related to the above facts.

Was this a bug introduced in 15.00.0400 that will be reversed?

InTheMood wrote:My old script worked for a few years, in XY.
Something changed in 15.00.0400.
15.00.0300 still works, using the original script.

My question was related to the above facts.

Was this a bug introduced in 15.00.0400 that will be reversed?

Confirmed. I recently (20150410) added an optimization that failed on the (slightly anarchic) syntax you are using. The next beta will work again as before.

admin wrote:Confirmed. I recently (20150410) added an optimization that failed on the (slightly anarchic) syntax you are using. The next beta will work again as before.

I completely understand, that for func( $parms ) there should be no blank in front of the first parentheses.

But, for example: how should it be for If( ... ) - is there the same rule, or is it something different?
(Just to verify. I'd expect: different situation.)

[expunged]

Sammay, before writing you should have a look at the documentation
It says: "Parentheses around the expression are mandatory."
(Yes: it's changed some time ago, and still works without.)
For Foreach and While it always was this way.
So there "might" be a risk that Don planned those to be without blank. Though I still don't think so.

I still wish(!) XY would notify users of such situations, so they could be corrected.
(Not long ago there was some discussion about "XY should handle syntax more strict". I think this belongs there...)

well, oops.