Retrieve string used for creating a thread

[think]

Is it possible to retrieve the string used for creating dll thread from the thread? In below case, can I retrive MyScript string later on?

Code: Select all

dll0:=ahkthread(MyScript)
MyScript:=""

[swagfag]

u could pass MyScript as a command line argument to the thread, then later use a combination of AhkGetVar and Alias to retrieve the thread's A_Args[1] which will contain the script u passed in

but why tho? u can simply store MyScript in ur main script when u create the thread for the first time. under what circumstances will u be unable to do so? also i think the method above can crash ur scripts if u do it with too many threads at the same time, but i havent checked

[HotKeyIt]

?

Code: Select all

ahkdll:=AhkThread("MsgBox this is my script")
MsgBox % ahkdll.ahkgetvar("A_LineFile")

[think]

HotKeyIt, thanks, this works, however I get Out of Memory error (or a Continuable Access Error) or the script simply freezes. Why would that be?
I know I could save the variable but it's very large and I thought I would save memory...

[think]

I also tried dll0.ahkReload() but it freezes the script too.

[HotKeyIt]

Can you upload an example?

[think]

It seems to be related to #if command. Press Alt+X couple of times.

Code: Select all

string:="
(
loop 100
{
	tooltip % A_Index
	sleep 100
}
return

#If Test()
#If

Test(){
; do nothing
return
}
)"

dll0:=ahkthread(string)
return

!x::
dll0.ahkReload()
return

[HotKeyIt]

That has been fixed now, thanks for the script.

[swagfag]

wait. why does A_LineFile return the thread's script contents. is this an ahk_h specific thing?

[HotKeyIt]

Yes

[swagfag]

couldnt find anything in the docs. are there more undocumented hidden vars/features such as this

[jeeswg]

@swagfag: I found it mentioned in the AHK_H v1 chm file (but not the v2 chm file). Cheers.

A_LineFile contains the full file path of currently running script (ahkdll + addFile) or the script as string/text (ahktextdll or addScript).

[swagfag]

whaat, theres a v1 chm file?
actually, i think i like this one better, think its more useful to have the docs document only the _h stuff and the differences from _l
i wonder what prompted the change