#OnAutoItStartRegister, practical use ???

[argumentum]

There is #OnAutoItStartRegister, and:
As the function runs before any of the main script code is executed, the function cannot reference any variables defined in an #include nor any variables defined as Global within the script. All variables within the function are treated as Local.

So, what practical use does it have ?

[Exit]

Even the example in the help file has errors.
MSGBOX () uses a variable that is in an include file and therefore results in an error.

MsgBox($MB_SYSTEMMODAL, "", "Function 'Example' is called first.")
MsgBox(^ ERROR

 

[mikell]

19 minutes ago, Exit said:

Even the example in the help file has errors.

Nice catch 
In the 3.3.14.2 help file, 4096 was still used but the later witch hunt for magic numbers did the job

[BrewManNH]

1 hour ago, argumentum said:

So, what practical use does it have ?

Perhaps you want to have a function to test something exists before starting the rest of the script, or to test for some other condition, rather than running the whole script and copying the includes into memory.

I've never used it, but it probably has some uses, about equal to the OnAutoItExitRegister which has similar usage needs questions.

[Danyfirex]

I've never used it before, I would use for initialize something. (DllOpen, Delete a log file, clean temp for something,etc)  But I will never use it because It's the first time I see it 😅

Anyway if you want to be able to use some of your global variables you could do something like this (I don't like the way/I will not use like that way. Its just a POC).

 

#AutoIt3Wrapper_AU3Check_Parameters=-q -d -w 1 -w 2 -w- 4 -w 6 -w- 7
#OnAutoItStartRegister "_Initialize"


#forcedef $g_Variable1, $g_Variable2
ConsoleWrite($g_Variable1 & " " & $g_Variable2 & @CRLF)

Func _Initialize()
    ConsoleWrite("_Initialize" & @CRLF)
    Assign("g_Variable1", "Hello", 2)
    Assign("g_Variable2", "World", 2)
EndFunc   ;==>_Initialize

 

Saludos