No, I remember not using ActiveX when doing that stuff.
And you probably already know this, but you can use Everything in ahk directly using its dll with DllCall, there are many examples out there, so there's no need to reinvent the wheel for that.
No, I remember not using ActiveX when doing that stuff.
And you probably already know this, but you can use Everything in ahk directly using its dll with DllCall, there are many examples out there, so there's no need to reinvent the wheel for that.
I know Everything SDK,
Here I just use es.exe as an example, Since many other .exe don't have a SDK.
The core issue is how to use this COM object in AHK script.
Hi. Many thanks @PolarGoose : I can confirm this now works fine again.
āFor the recordā, it definitely used to work at some point before I reported the issue (without any change to the scripts or the applications called). Iām not convinced thereās much to gain to try and dig further than itās been done on your side or on Opus side to try and find what changed.
Works fine now, many thanks one more time for putting the time and effort into this extension and its maintenance!!
Update 13.17.9 introduces FSUtil.Run() which seems to do something similar to @PolarGoose ās project, including
exitcode: exit code of the process
stdout: data written to stdout
stderr: data written to stderr
Is this the beginning of the end of the Scripting Extension project or just the end of the beginning of it?
Is this the beginning of the end of the Scripting Extension project
Luckily, not. Reasons:
DOpus-Scripting-Extensions
has other functionality.ProcessRunner
has a better way to pass parameters if they contain spaces or quotes. Also, I haven't tested the performance difference yet.As a guideline, you should use FSUtil.Run
. I will keep ProcessRunner
for backward compatibility purposes.
I don't want to support AutoHotkey in the DOpus-Scripting-Extensions
, especially as we have FSUtil.Run
now.
It is much better to create a separate DLL for AutoHotkey. As AutoHotkey has DllCall
, there is no need to register a COM DLL, and thus, a better solution can be created.
I will try to make a separate DLL for AutoHotkey. I think it might be useful for the AutoHotkey community.
I have created a separate DLL for AutoHotkey:
AutoHotkey-ProcessRunner-dll
It provides the same functionality, but in a way that is more convenient to use from AutoHotkey.