well here we goes

[Tomb]

with a script in uncompiled form, you can keep some of your functions in a seperate script / text file. similar to how a UDF works. like for example if i had a file called text.txt and in this file i had wriiten

Func TestFunction()
MsgBox(0, "", Hello.  This is just a test")
EndFunc

now if i had a seperate .au3 script that called that function, and i wrote #Include "text.txt" like this example

#Include "Text.txt"

TestFunction()

now i can make use of the function in my seperate file.

and if you were to compile the main script, the Text.txt function would be included into my script.

this making the compiled script a standalone .exe

but, what i want to do is have a script that includes a file similar to Text.txt in my example above, but without including it in the script once compiled. I would like the newly compiled script to still reference to a text file from which the functions could be edited in at a later time.

very similar to how it can reference the text.txt in uncompiled form.

ofcourse, if the file was not existing, there would be a problem, but lets just assume i will always have it right there.

i thought of just using like fileread or iniread but then i soon realized it wouldn't work for the functions properly.

[NELyon]

Execute()

[Tomb]

Execute()

I think that might just work.

just wish my autoit helpfile had a better example for executing functions.

i am going to search for an example of execute, i believe the answer is somewhere located in this function.

thanks

Edit: i spelled helpfile wrong.

Edited April 16, 2008 by Tomb616

[Tomb]

ok hmm i didn't figure it out.

i did find a term that makes more sense to describe what i'm trying to accomplish though.

Executing a External Function.

[Tomb]

[FreeFry]

So basically what you want(in the long run) is to define a function, after that the script is run, at run-time ?

[Tomb]

So basically what you want(in the long run) is to define a function, after that the script is run, at run-time ?

well, the function could be defined previous to running the script.

but also edited during running yes.

[FreeFry]

Well you can't really "edit" a function after it has been run.

You can modify how/what the script executes/does, but not modify the function after runtime...

Only way to do that would be to write the code of the function to a .au3 file, then run that script with the AutoIt commandline parameters...

[MrCreatoR]

I think he wants to be able change the function (in external module or something) even after the script is compiled...

@Tomb616

You can write the needed functions and they execution to some file (module), for example «External_UDFs.fnc»:

expandcollapse popup

#NoTrayIcon

If $CmdLine[0] = 0 Then Exit ;We need at least 1 command line


;Collecting parameters
$sParams = ""

For $i = 2 To $CmdLine[0]
    $sParams &= $CmdLine[$i] & "|"
Next

$sParams = StringTrimRight($sParams, 1)

Call($CmdLine[1], $sParams)


;==== UDFs Part ====

Func Some_UDF($sParams)
    Local $iRet = MsgBox(36, "Question", $sParams)
    
    ConsoleWrite($iRet)
EndFuncoÝ÷ Ø Ý¶§Ê«r©W±Êâ¦Ü"Yh¢K,¢g­)à)¶¬jëh×6Global $sUDFs_Module = @ScriptDir & "\External_UDFs.fnc"

$vRet = _ExecuteExternalFunc("Some_UDF", "test")

MsgBox(64, "", "Returned Message from ExternalFunc: " & $vRet)

Func _ExecuteExternalFunc($sFuncName, $sParams="")
    Local $iPID = Run(@AutoItExe & ' /AutoIt3ExecuteScript "' & $sUDFs_Module & '" ' & $sFuncName & ' ' & $sParams, '', '', 2 + 4)
    Local $sStdOutRead = ""
    
    While ProcessExists($iPID)
        $sStdOutRead &= StdoutRead($iPID)
    WEnd
    
    Return $sStdOutRead
EndFunc

Edited April 19, 2008 by MsCreatoR

[Tomb]

thanks MsCreator.

that is very useful