Shared Variables

[zasxes]

Is there a way to have 2 scripts running and have them use variables that are set in only one script?

For instance:

Script one:

$VAR = 0

While 1

$VAR = $VAR+1

Wend

Script two:

While 1

$GETVAR1=$VAR

Sleep 10000

$GETVAR2=$VAR

If $GETVAR1 = $GETVAR2 then

do something

endif

Wend

[Jos]

You could use an INI file..

Check out INIWRITE and INIREAD....

[zasxes]

I figured I could do that I just wanted to do it all in memory

[trids]

Now THERE's a good idea .. yes, we could have AutoItWinSetValue and AutoItWinGetValue ..

Awesome!

[Nutster]

How? Named pipes? File Semephores? Temp files?

Get from where? Send to where? What if more than two processes were running and wanting to share information?

Hmm, a named pipe could work... I will investigate on the weekend.

The process that sends the value would create the pipe and put the result of the expression on it, and close/forget its end of it. The other process would look for the pipe with a timeout. If no value was forthcoming in time, set @Error to 6 for example. If it finds the pipe, take the value, close the pipe entirely and return the value.

Oh, yeah, this is UNIX feature. I don't know if Windows allows this. Oh, well I know how to find out.

Hopefully,

AutoItWinSetValue("Pipe Name", <exp[b][/b]ression>)
$x=AutoItWinGetValue("Pipe Name")

[Valik]

David, yes, Window's has named (and unamed) pipes. I've not used them, though. Thought about using them in a project... but I've not actually started that project so I've not done any reading on them.

Edit: I should also mention that I wouldn't mind seeing pipes so that there could be interprocess communication in a very clean way.

Edited June 5, 2004 by Valik

[CyberSlug]

In my opinion, this is how EnvSet and EnvGet should work.

[Nutster]

True, but the environment is inherited from one process to its children. Named pipes can be used by anybody, related or not; you just have to know the name of the pipe.

Unnamed pipes are also parent/child communication only.