Long startup .exe

[ravett]

Hello

It is very important that the script runs as soon as possible.

If the script is run from the Macro application, then it comes out much (about 1-2s), faster than running the .exe file.

But it turned out that it is necessary to run from .exe.

How can you speed up this moment?

[Grovkillen]

My experience is the opposite. Compiled macros run faster than from within the editor.

[ravett]

My experience is the opposite. Compiled macros run faster than from within the editor.

Hmm ...

What is usually associated with the startup speed of .exe?

[Grovkillen]

Depends on what commands your script is using.

[ravett]

Depends on what commands your script is using.

My script is 2 lines)

Press Shift
Press F3

It seems that the matter is not in the script, but in the .exe itself
The script works quickly.
It takes a long time to start.

I wonder why the executable file is more than 2MB?

[Grovkillen]

The exe contains the "engine" to run your script. So the minimum size will always be around 2.2MB.

[ravett]

The exe contains the "engine" to run your script. So the minimum size will always be around 2.2MB.

I made the same script (if I can call it 2 lines ) in AutoHotKey and created an executable .exe file in it

It starts much faster there.

So it's not about the power of the PC as I thought before.

[Grovkillen]

I rarely use keyboard commands so i cannot tell but I don't see any delay at all. Perhaps the "engine" is adding a small delay when using the keyboard commands?

[Marcus Tettmar]

It is logical that compiled macros will take longer to start than macros in Macro Scheduler where Macro Scheduler is already running.

An analogy would be: opening a word document by double clicking the document when Word is not already opened vs opening a word document from within word which is already open. You'd expect the latter to be quicker because Word itself is already open.

Running a compiled macro requires the macro interpreter to load. When Macro Scheduler is running everything the script needs to run is already present.

But that said, as others have noticed here, any delay is barely negligible to most humans on most systems

[PepsiHog]

Hello,
Just reading this post, I thought maybe the problem is really it's running too fast. Have you tried adding a delay as the first line? Not much just maybe .5 or .2 (wait>.2)

You may also want to add a ridiculous delay, just for testing purposes. You could also add a mdl> at the start so you can visually see when it started.

It also occurs to me that you are not setting any focus. You are just throwing it out there and hoping the right "thing" catches it. Could something else be absorbing the strokes?

PepsiHog

I also have never experienced anything of this nature with exes.