XYplorer Beta Club

Hey jacky,

very nice work on the POM there in the XYwiki!

http://88.191.26.34/XYwiki/index.php?ti ... th_Menu.29

Thanks
I have to say this feature is growing on me, well done!

Though, to be honest, I still think it would have been a really nice thing for PFA to support parameters, so instead of using
[pattern]>"Caption" [application]
you would have used
"Caption" [pattern]>[application]

Then we could have used quotes in the application field, and so parameters on the command line. Sure, it can be worked around using scripts, but it means (a) we need to use a caption whereas the app's name would have been found by XY otherwise, and (b) we get a script icon instead of the one for the application used to open the item(s), and really it's not a script to just add something like "/fullscreen" on some command line, is it?

jacky wrote:Thanks
I have to say this feature is growing on me, well done!

Though, to be honest, I still think it would have been a really nice thing for PFA to support parameters, so instead of using
[pattern]>"Caption" [application]
you would have used
"Caption" [pattern]>[application]

Then we could have used quotes in the application field, and so parameters on the command line. Sure, it can be worked around using scripts, but it means (a) we need to use a caption whereas the app's name would have been found by XY otherwise, and (b) we get a script icon instead of the one for the application used to open the item(s), and really it's not a script to just add something like "/fullscreen" on some command line, is it?

Okay, please explain again in other words: what do you miss? Is it that you want to add command line parameters? Give an example. (I might have another way to achieve the same...)

admin wrote:Okay, please explain again in other words: what do you miss? Is it that you want to add command line parameters? Give an example. (I might have another way to achieve the same...)

Yes, right now on PFA we can only give an application's (path/)name, and I'd like to add command line parameters.

For example I've got one app I'd like to add "/fullscreen /monitor 2" on the command line, so I don't have to always manually move the window to the next monitor and put it to fullscreen mode ; Also I have PFAs for ZIP & RAR files that use command line parameters so I get "Extract Here" & "Extract Each to Subfolders" commands there. I have Open With UDCs for those two commands already as well, which I intend to keep for the KS, but this would be a nice way to get the same commands quickly available through mouse.

I thought of using quotes because that's how it works on UDC: putting the app in quotes allow us to follow it by command line parameters (which can even include <item1> & <item2> or <items>, which is nice, though not actually needed for my own needs, but if possible I'm sure it could be useful to others)

jacky wrote:

admin wrote:Okay, please explain again in other words: what do you miss? Is it that you want to add command line parameters? Give an example. (I might have another way to achieve the same...)

Yes, right now on PFA we can only give an application's (path/)name, and I'd like to add command line parameters.

For example I've got one app I'd like to add "/fullscreen /monitor 2" on the command line, so I don't have to always manually move the window to the next monitor and put it to fullscreen mode ; Also I have PFAs for ZIP & RAR files that use command line parameters so I get "Extract Here" & "Extract Each to Subfolders" commands there. I have Open With UDCs for those two commands already as well, which I intend to keep for the KS, but this would be a nice way to get the same commands quickly available through mouse.

I thought of using quotes because that's how it works on UDC: putting the app in quotes allow us to follow it by command line parameters (which can even include <item1> & <item2> or <items>, which is nice, though not actually needed for my own needs, but if possible I'm sure it could be useful to others)

And if you just link the PFA to your UDC via command ID (à la ::#1444)? That way you have just one place with the definition -- easier to manage.

admin wrote:And if you just link the PFA to your UDC via command ID (à la ::#1444)? That way you have just one place with the definition -- easier to manage.

Yeah, but :
- I don't have UDCs for all such PFAs. For WinRAR yes, not for others
- It remains the same : script icon instead of app's icon, ...

Unless when a PFA is "linked" to an Open With UDC, XY would recognize it and get the app's name & icon. In such case, sure, of course!

jacky wrote:

admin wrote:And if you just link the PFA to your UDC via command ID (à la ::#1444)? That way you have just one place with the definition -- easier to manage.

Yeah, but :
- I don't have UDCs for all such PFAs. For WinRAR yes, not for others
- It remains the same : script icon instead of app's icon, ...

Unless when a PFA is "linked" to an Open With UDC, XY would recognize it and get the app's name & icon. In such case, sure, of course!

Okay, I'll see...

admin wrote:

jacky wrote:Unless when a PFA is "linked" to an Open With UDC, XY would recognize it and get the app's name & icon. In such case, sure, of course!

Okay, I'll see...

It would be nice if Catalog items were also capable of this.

TheQwerty wrote:It would be nice if Catalog items were also capable of this.

hmm.. but they can. Or, you mean the "link" with UDCs being recognized and treated as such (icon wise), right ?

Because you can create a new Catalog item, set its action as "Open selected List item(s) with Application", and in Application put the app's name between quotes, followed by the command arguments you wanna use, etc Basically, it's exactly the same as an UDC Open With.

jacky wrote:

TheQwerty wrote:It would be nice if Catalog items were also capable of this.

hmm.. but they can. Or, you mean the "link" with UDCs being recognized and treated as such (icon wise), right ?

Because you can create a new Catalog item, set its action as "Open selected List item(s) with Application", and in Application put the app's name between quotes, followed by the command arguments you wanna use, etc Basically, it's exactly the same as an UDC Open With.

I mean the linking.. so that we could truly manage all the Open Withs in a single place (UDC) and not sacrifice the custom icons, etc.

TheQwerty wrote:

jacky wrote:

TheQwerty wrote:It would be nice if Catalog items were also capable of this.

hmm.. but they can. Or, you mean the "link" with UDCs being recognized and treated as such (icon wise), right ?

Because you can create a new Catalog item, set its action as "Open selected List item(s) with Application", and in Application put the app's name between quotes, followed by the command arguments you wanna use, etc Basically, it's exactly the same as an UDC Open With.

I mean the linking.. so that we could truly manage all the Open Withs in a single place (UDC) and not sacrifice the custom icons, etc.

I'm not sure what you mean by "not sacrifice the custom icons"...

admin wrote:I'm not sure what you mean by "not sacrifice the custom icons"...

You suggested using UDC to manage "Open With" commands and then just using scripting in PFA to access those.

The problem as jacky pointed out is you then lose the icons and are stuck with a lot of scripting arrows.


I'm suggesting if you find a fix for that for PFA/POM then you should also look at fixing it for the Catalog. That way we could truly manage Open Withs in a single place that could be called everywhere else, and in those places it would use the correct icon instead of the scripting arrow.

TheQwerty wrote:

admin wrote:I'm not sure what you mean by "not sacrifice the custom icons"...

You suggested using UDC to manage "Open With" commands and then just using scripting in PFA to access those.

The problem as jacky pointed out is you then lose the icons and are stuck with a lot of scripting arrows.


I'm suggesting if you find a fix for that for PFA/POM then you should also look at fixing it for the Catalog. That way we could truly manage Open Withs in a single place that could be called everywhere else, and in those places it would use the correct icon instead of the scripting arrow.

Okay, I understand the part with the icon (although I've not decided yet about it).

When you say "find a fix" you're talking about support for parameters? This is not a bug, it's a new feature that has to be added...

Ah, nice examples there on the new timestamp command!
http://88.191.26.34/XYwiki/index.php/Sc ... _timestamp

well done, monsieur jacky!

Ah, FVS is now in the XYwiki!

http://88.191.26.34/XYwiki/index.php/Fo ... w_Settings

I did not want to edit your work , wiki master, but I think this info box should be obsolete now:
"It is very important that you put the last backslash ( \ ) when specifying folders' path/names ..."
XY will provide the backslash if it's missing so you don't have to care!

I'm afraid you also need a new screen shot for the Edit dialog... because the Applied settings have been changed today. Upload comes in a minute...

Thanks, man!