XYplorer Beta Club

jacky wrote:Well, despite the case issue, one thing is broken though : registered applications.

We used to be able to specify a registered application by quoting it, eg. by putting "winrar" or "notepad" (quotes included) no need to specify a path. Well, this doesn't work anymore, as ::open """notepad""" gets this:
Couldn't find application:
D:\Program Files\XYplorer\notepad

PS: Works fine for openwith but not with open, although it's required with open as well to send parameters to the app!

Fixed & uploaded.

admin wrote:

TheQwerty wrote:

admin wrote:

TheQwerty wrote:It's all broke.

With 6.80.0075 XY's not recognizing most commands.

For example?

Nothing.. as I said in the edit, you just made it case sensitive. (Boo!)

Whoops, not on purpose! Fix is coming...

Yay! All good! For a moment there, I was afraid I'd have to make a wish to get that back.

Now to put this hiding script feature to the test and hopefully clean up my scripts a little.

admin wrote:Fixed & uploaded.

Yeah, you're on a roll lately!

New little things : On CKS, the options to copy(-append) command IDs still use the old syntax (::#XXX::#XXX)

BTW, I kinda wish UDC would have the same features, so a label/btn "Command #XXX" instead of a textbox, with same ctxt menu...

jacky wrote:BTW, I kinda wish UDC would have the same features, so a label/btn "Command #XXX" instead of a textbox, with same ctxt menu...

Good, I never like the textbox anyway. But what, where, how? You mean a button "Options..." that pops a menu with which commands?

admin wrote:Good, I never like the textbox anyway. But what, where, how? You mean a button "Options..." that pops a menu with which commands?

Well, my first idea was a button with caption "Command #XXX" so that we can see the command ID if that's all we want to do; but then clicking it would popup the menu with options copy & copy(-append) command ID.

Or you could use a simple label that one must right-click to popup that menu, and add the same menu also on CKS for consistency sake, but the button idea makes it "obvious" for people that there's more to it...

<pita>Looks good. Though I could say, it might be a good idea to have the exact same button on both CKS & UDC, only for consistency sake...</pita>

Question, but i think it's a bug : why can't i do this: ::sel """*.txt""" to select&focus the first item to be a text file ? Somehow it refuses to work, though ::sel """*.txt*""" will work (but not really the same...).

jacky wrote:<pita>Looks good. Though I could say, it might be a good idea to have the exact same button on both CKS & UDC, only for consistency sake...</pita>

Question, but i think it's a bug : why can't i do this: ::sel """*.txt""" to select&focus the first item to be a text file ? Somehow it refuses to work, though ::sel """*.txt*""" will work (but not really the same...).

Oh, yes a bug. Fixed. Merci bien!

admin wrote:

jacky wrote:<pita>Looks good. Though I could say, it might be a good idea to have the exact same button on both CKS & UDC, only for consistency sake...</pita>

Question, but i think it's a bug : why can't i do this: ::sel """*.txt""" to select&focus the first item to be a text file ? Somehow it refuses to work, though ::sel """*.txt*""" will work (but not really the same...).

Oh, yes a bug. Fixed. Merci bien!

BTW: ::sel """*.txt""" looks ugly with all those quotes. The argument is a bit overloaded for my taste. And quoting as a marker is not so good.

What about this instead:
::sel [*.txt]

admin wrote:BTW: ::sel """*.txt""" looks ugly with all those quotes. The argument is a bit overloaded for my taste. And quoting as a marker is not so good.

What about this instead:
::sel [*.txt]

Well, once you're used to it those 3 quotes don't really bother me...

Anyhow, wouldn't that look a bit weird to?
::sel "[[bdc]*]"

Yeah, no, it might be better, you're right.

Question: If you cancel on the input (_foo) the rest of the calling script is still executed, is that the best ? Shouldn't the entire "running" script be aborted, i.e. all calling scripts as well ?
Especially since it may be that, or some error after a goto (location ot found)...

Not to mention it's weird to press "Ok" on a "The script is terminated now" or "The Script ends here" message, only to see it continuing...

jacky wrote:Question:

Code: Select all

"_foo"
 input foo, foo?;
"_bar"
 msg foobar;

"Foobar"
 sub _foo;
 sub _bar;

If you cancel on the input (_foo) the rest of the calling script is still executed, is that the best ? Shouldn't the entire "running" script be aborted, i.e. all calling scripts as well ?
Especially since it may be that, or some error after a goto (location ot found)...

Not to mention it's weird to press "Ok" on a "The script is terminated now" or "The Script ends here" message, only to see it continuing...

Hmm, good point. Currently it's totally self-contained. Scripts can call up other scripts, but no script knows of its callers nor callees. "The Script ends here" should read "The script stack now pops down one level".

I guess you are right: the whole stack should die.

jacky wrote:<pita>Looks good. Though I could say, it might be a good idea to have the exact same button on both CKS & UDC, only for consistency sake...</pita>

About that button : when no UDC is selected, it's not disabled but caption-less, and we get this: #0;#0;

Well, I found a way to get things (Tabs) pretty messed up it seems !

It invoves cycling through tabs with delay, and Finding Tabs. Cycling though tabs, at first with delay so List doesn't get updated, and without delay for the last one so List gets updated; and then moving back to the start point. And it seems important that at least one tab in the mix is a Finding Tab.

Doing that somehow gets tabs in the middle to get their location confused, and that even when when they were (home) locked. Finding Tab may show locations, Browsing tab may show search results, or just other locations even though they're not their locked location (or in their home zone when home locked)...

So yeah, it's quite of a mess.

SubSubject: Inconsistent Regular Expression Intervals syntax

Using v6.80.0078, interval expressions are parsed with spaces instead of commas. For example: Rename re, ^a{1 2} ... $. Whereas, in Find Files/Name & Location, you must use this form of expression: a{1,2}.*.

msalvatori wrote:SubSubject: Inconsistent Regular Expression Intervals syntax

Using v6.80.0078, interval expressions are parsed with spaces instead of commas. For example: Rename re, ^a{1 2} ... $. Whereas, in Find Files/Name & Location, you must use this form of expression: a{1,2}.*.

No. You have to quote any argument that contains commas or semicolons (since they are separators in scripting). So you should do Rename re, "^a{1 2} ... $"