Necessary to determine the launch of the AutoHotkey script

[mike2003]

I want to know whether a certain AutoHotkey script is running or not. To do this, I used the "autohotkey.exe" command line definitions. The code from here:

But it takes a very long time, 1-2 seconds. Can this be accelerated?

Function _WinAPI_GetProcessCommandLine does not work. It returns emptiness.

[AlessandroAvolio]

If the file is running why don't you use ProcessExists?

[mike2003]

8 hours ago, AlessandroAvolio said:

file is running

Because I need a specific script, not just a file.

Edited October 5, 2021 by mike2003

[AlessandroAvolio]

3 minutes ago, mike2003 said:

what?

Is your script running as an executable file?

[mike2003]

no

[Danp2]

9 hours ago, mike2003 said:

Function _WinAPI_GetProcessCommandLine does not work. It returns emptiness.

Have you tried the example in the help file? Seems to work correctly when I run it.

[mike2003]

9 hours ago, mike2003 said:

Function _WinAPI_GetProcessCommandLine does not work. It returns emptiness.

 

[mike2003]

[Danp2]

Ok... Have you tried examining the command line using ProcessExplorer? Also, can you show us your existing code that you are wanting to run faster?

[mike2003]

I use Process Hacker, I see everything. All codes are in the examples above.

Edited October 6, 2021 by mike2003

[Danp2]

Good luck

[Danp2]

@mike2003You ask for help without providing many details, which requires that we repeatedly ask questions to obtains the necessary details. You make statements, such as

On 10/5/2021 at 7:04 AM, mike2003 said:

Function _WinAPI_GetProcessCommandLine does not work. It returns emptiness.

without providing any proof or code to substantiate your claim. I asked you to show us your existing code, and your response is to refer me to a 7 year old thread where you supposedly obtained the original code.

Why should others take the time to try to help you when you aren't willing to take the time to provide the requested info? 😩