Using external scipts to hold code

[dinodod]

I was wondering how I could best seperate my GUI from the functional code. I see the Include command & Call command but is there any way to call a function from an external file?

The Include command will execute the .au3 file and terminate. What i am trying to do is hold all my functions in a external file and simply call the function from my main file.

Is there such a way to do that? If not, is there a way to load the external file and hold it in memory (Include terminates the file when it's done)

Thanks!

[Valuater]

I was wondering how I could best seperate my GUI from the functional code.  I see the Include command & Call command but is there any way to call a function from an external file?

The Include command will execute the .au3 file and terminate.  What i am trying to do is hold all my functions in a external file and simply call the function from my main file.

Is there such a way to do that?  If not, is there a way to load the external file and hold it in memory (Include terminates the file when it's done)

Thanks!

<{POST_SNAPBACK}>

I think this is what your looking for

fist save this file as "messageBox.au3" and place it in the "include" folder of Autoit

Func MESSAGEBOX()
    MsgBox(0,"TEST", "This is an include functuion test... OK")
    
EndFunc

then here is the gui... note it has the include message box at the top

#include <GUIConstants.au3>
#include <MessageBox.au3>

GUICreate("My GUI Button") ; will create a dialog box that when displayed is centered

Opt("GUICoordMode",2)
$btn_ok = GUICtrlCreateButton ("OK",  10, 30, 50)
$btn_cancel = GUICtrlCreateButton ( "Cancel",  0, -1)

GUISetState ()    ; will display an  dialog box with 2 button

; Run the GUI until the dialog is closed
While 1
    $msg = GUIGetMsg()
    
    If $msg = $GUI_EVENT_CLOSE Or $msg = $btn_cancel  Then ExitLoop
        
    If $msg = $btn_ok Then
        call("MessageBox")
    EndIf
Wend

i tested this and it works..... hope it helps

8)

[dinodod]

Interesting.. From my reading in the help file, I thought it would load the file & terminate it. Thanks for clearing that up.

Here is the Help File example:

;;; TIME.AU3 ;;;

MsgBox(0,"", "The time is " & @HOUR & ":" & @MIN & ":" & @SEC)

;;; SCRIPT.AU3 ;;;

#include "TIME.AU3"

MsgBox(0,"", "Example")

#include "TIME.AU3"

Exit

; Running script.au3 will output three message boxes:

; one with the time, one with 'Example', and another with the time.

[Hooch]

I seperate all my code into seperate files and stick them in a /bin directory under my main script directory and just include them at the top of my parent script file like this:

#Include <gui_Constants.au3>
#Include <bin\functions.au3>
#Include <bin\gui_Main.au3>

[Sokko]

I suppose that from a technical standpoint, calling a file with #include does indeed load, run, and terminate it. The point that the example fails to mention is that any functions or variables defined in the included script will remain in memory for the rest of the main script. This is an easy way to load large sets of user-created functions, or to assign names to a large number of constants for greater ease of use (like in GUIConstants.au3).

[SmOke_N]

I believe Snake wrote a UDF that trims the #include variables to just what that script needs.

[quaizywabbit]

I suppose that from a technical standpoint, calling a file with #include does indeed load, run, and terminate it. The point that the example fails to mention is that any functions or variables defined in the included script will remain in memory for the rest of the main script. This is an easy way to load large sets of user-created functions, or to assign names to a large number of constants for greater ease of use (like in GUIConstants.au3).

<{POST_SNAPBACK}>

if you have compiled an exe that uses #include(s) , decompile it and you'll see that the included script is literally merged into the main script starting at the line # the #include was on

[MHz]

I seperate all my code into seperate files and stick them in a /bin directory under my main script directory and just include them at the top of my parent script file like this:

#Include <gui_Constants.au3>
#Include <bin\functions.au3>
#Include <bin\gui_Main.au3>

<{POST_SNAPBACK}>

Whenever i look into a bin directory, I normally find binary files. Seems to be a custom for bin folders.