XYplorer Beta Club

highend wrote:Any workaround available?

Yes, but not ideal IMO.
Not really because of the PFA catchall per se, but because of the use of PFA>Script.

@all
AFAIK, any PFA that runs a script raises two issues with:
1. The "Open" SC command
2. The "Open" function used in User>Manage Commands, and in Catalog

Workarounds:
1. Replace your e.g. "open <curitem>" command in code with the following:
perm $EXTCLICK = "<curitem>"; load "PowerLauncher.xys"; unset $EXTCLICK;
2. Copy/Paste the exact line from "Open" items into "Open With" items. (should work with AutoHotkey example)

So you should have the possibility to have everything working, but it doesn't fell right though, since PFA>Script is kind of breaking the official "Open" tools...

If anyone has an idea, you're more than welcome!
A new <openitem> perhaps? Since there's already some parsing between Catalog/UserCommands and PFA...

Hi highend,
I was just curious as to why you are using XY to start a AHK script instead of the other way around. I ask because I know, that you know, you could easily have AHK detect when XY is active and have any kind of AHK keyboard shortcuts to run XY commands/scripts/KSs. Do you want to avoid having AHK in Windows start-up or do you only use AHK associated with XYplorer? AHK is quite light resource wise.
Ken

Update: For Multiple Application definitions, CommandLine applications were not detected. So this line must be further expanded. Now scripts are also detected instead of only "allowed" (& yep, I like brackets ) So now, Multiple Applications work fine, for apps w/ or w/o CL, and scripts w/ or w/o CL.
Apps with CL have a warning icon, but that's the price to pay to see the command-line arguments...
I also updated the script with a better warning for app(s) defined but not found, but I'll upload it when things are a little out of "alpha" status.

Hi Ken,

It's just an entry for my personal convenience I usually compile my .au3 / .ahk scripts, but this one is under constant development, so I'm too lazy to compile it each time I've made a change. When this one is finished some day, I'll remove it from XY and put it in the autostart folder.

@FluxTorpedoe

2. Copy/Paste the exact line from "Open" items into "Open With" items. (should work with AutoHotkey example)

Works. Thanks a lot!

I also updated the script with a better warning for app(s) defined but not found, but I'll upload it when things are a little out of "alpha" status.

I'd call it at least "beta"

highend wrote:I'd call it at least "beta"

Well, as you noticed, code needs some make-up to cover its traces...

Anyway, I'm still trying to wrap my head around the PFA > Script conundrum...
Can't find another way out than a new variable. Time for a new Wish then.

Hi'

FluxTorpedoe wrote:I'm still trying to wrap my head around the PFA > Script conundrum

Well, Don solved it for me!

So here's a "private" version using the new var <pfaitem>.
I've everything opened by a PFA catchall:
*.*>::load "PowerLauncher.xys";
and it's now working great in all cases, whether via List, UDC, Catalog, etc... and of course still via PowerLauncher button itself.

Power Launcher v1.6 beta 1 - Requires XYplorer >= v12.30.0103Note: This script still requires the use of its Definitions file found in the first post.

 
#####################
###  Power Opener v3.40  ###
#####################
(Formerly known as Power Launcher)

Hi everyone,

Here’s a new version with some major changes.
See full list in Changelog.

Important info for users who update:
— Both files must have the same name: PowerOpener.xys and PowerOpener.ini
— You must edit your definition file (PowerOpener.ini), which do not use *. for file types
   All info available in the new (blank) definition file below.

I apologize for the lack of clear instructions.
Unfortunately, I’m currently busy and will be offline for a few months. But I’ll check all messages when I return.

I hope it’s still of some use as it is.

Have a nice day,

    Flux

———————————————————————————

• DOWNLOADS:   (previous versions available in Changelog)

› Script: › Definition file:
———————————————————————————

• INSTALLATION » for first-time users:
 — Please refer to first post

• UPDATE » for all users:
 — Copy "PowerOpener.xys" and its unzipped definition file "PowerOpener.ini" to your scripts folder
 — Copy your old settings into the definition file