Script - Limit to one copy running at a time

[gsb]

Script - Limit to one copy running at a time so subsequent instantiations exit quietly,

or maybe set the previous one's tray icon to blink for a few seconds and then exits

So I am learning by examples, help file and docs.

Question. Here is a most simple script.

#Include <Constants.au3>
#NoTrayIcon

TraySetToolTip("This is my new tooltip text!")
TraySetState()

While 1
    Sleep(10); Idle loop
WEnd

Exit

How can I insure that only one is running at a time?

That is, if by mistake I forget to exit the running script before I start the script again, I want the second instance to check and if there is already a copy running simply exit the script.

How would I set up such a check?

Thanks,

gsb

[The Kandie Man]

Use the _Singleton function. Search for it in the documentation. This function makes it so that only one script can be run at a time.

Here is the example from the help file:

#include "Misc.au3"
if _Singleton("test\test",1) = 0 Then
    Msgbox(0,"Warning","An occurence of test is already running")
    Exit
EndIf
Msgbox(0,"OK","the first occurence of test is running")

[gsb]

Thank you The Kandie Man.

It is tough finding the things I do not yet know about.

I will look it now.

gsb

[Cue]

you should have found in the FAQs

$Mytitle = "your window name"
If WinExists($Mytitle) Then Exit
AutoItWinSetTitle($Mytitle)

add this to the top of the script before anything else

[Paulie]

you should have found in the FAQs

$Mytitle = "your window name"
If WinExists($Mytitle) Then Exit
AutoItWinSetTitle($Mytitle)

add this to the top of the script before anything else

Test your scripts before posting.

There are so many ways that could fail

EDIT: his script doesn't even have a window! how will that help him?

@gsb

Use '_Singleton'

Edited October 15, 2006 by Paulie

[Valik]

Test your scripts before posting.

There are so many ways that could fail

EDIT: his script doesn't even have a window! how will that help him?

@gsb

Use '_Singleton'

While using Singleton() is the way to go, you should make sure you know what you're talking about, too, before you go lambasting somebody. Not only does the code work as demonstrated, it is the example in the help file for this very thing.

[MHz]

EDIT: his script doesn't even have a window! how will that help him?

Indeed it does have a window. Every AutoIt3 script has a hidden window.

Edit:

This will show the window

WinSetState(AutoitWinGetTitle(), '', @SW_SHOW)
Sleep(10000)

Edited October 15, 2006 by MHz

[Paulie]

While using Singleton() is the way to go, you should make sure you know what you're talking about, too, before you go lambasting somebody. Not only does the code work as demonstrated, it is the example in the help file for this very thing.

I understand, and i never meant to suggest the code wouldn't work

But the code was not really the best for the task the OP intended it to be used for, though it may work, it is easily thrown off by unpredictable things such as other windows.

If i was too harsh i apologize, but i don't think that basing something like this on window titles is a very reliable method. Especially when others (Singleton) exist.

@MHz

Learn something new every day i guess...

Edited October 15, 2006 by Paulie

[shaamaan]

Script - Limit to one copy running at a time so subsequent instantiations exit quietly ...

try this:

If @Compiled = 1 Then
   $list = ProcessList(@ScriptName)
   If $list[0][0] > 1 Then Exit
EndIf

[gsb]

Sorry to cause trouble.

I am learning.

I did look through the FAQ and lots more so far.

But I did not know that such a script has a "hidden" named window.

_Singleton is working fine; but is shaamaan's code even better?

If @Compiled = 1 Then
   $list = ProcessList(@ScriptName)
   If $list[0][0] > 1 Then Exit
EndIf

Better as in efficiencies. These things I do not know yet.

Thank you everyone for your help.

I do appreciate it.

gsb

[Jos]

Sorry to cause trouble.

I am learning.

I did look through the FAQ and lots more so far.

But I did not know that such a script has a "hidden" named window.

_Singleton is working fine; but is shaamaan's code even better?

It works assuming your program name is unique but with Singleton you are 100% sure about the fact that this program only runs once. Edited October 15, 2006 by JdeB

[gsb]

Thank you.

I shall leave it as _Singleton.

gsb

[Valik]

try this:

If @Compiled = 1 Then
   $list = ProcessList(@ScriptName)
   If $list[0][0] > 1 Then Exit
EndIf

Worst way ever conceived. You really should be shot multiple times for even suggesting this (My standard reaction to that particular code).

[Cue]

Wow, seems that this post really heated up while i was away.

@Paulie

I know you did not mean to be harsh but to say

Test your scripts before posting.

when infact you have not tested mine seems a bit hypocritical

you also said

EDIT: his script doesn't even have a window! how will that help him?

later saying

i never meant to suggest the code wouldn't work

which slightly contradicts what you said earlier

Anyway, I do not mean to cause an argument. I for 1 didnt know about _singleton and didnt consider the other option failing if another window with the same name already existed so thank you for pointing that out.

Worst way ever conceived. You really should be shot multiple times for even suggesting this (My standard reaction to that particular code).

Edited October 17, 2006 by Cue

[Paulie]

Wow, seems that this post really heated up while i was away.

@Paulie

I know you did not mean to be harsh but to say

when infact you have not tested mine seems a bit hypocritical

you also said

later saying

which slightly contradicts what you said earlier

Anyway, I do not mean to cause an argument. I for 1 didnt know about _singleton and didnt consider the other option failing if another window with the same name already existed so thank you for pointing that out.

You're right, i did contradict myself, but when i said that, i didn't know that every script actually had a window that was just hidden.

But singleton is definitely the way to go. I use it often

Edited October 17, 2006 by Paulie

[Tentaal]

There is something I dont understand with _Singleton.

I have thos code

Func IsAlreadyRunning()
if _Singleton("Killwirelessv2.exe",1) = 0 Then
    Msgbox(0,"Error","Programm is already running.")
    Exit
EndIf
EndFunc

When I lauch killwirelessv2.exe a second time, I get the message "Programm is already running".

But.. If I change the code like this, for example :

if _Singleton("Killwir.exe",1) = 0 Then

it is still working!

Why??

Tnanks.

[Jos]

There is something I dont understand with _Singleton.

I have thos code

Func IsAlreadyRunning()
if _Singleton("Killwirelessv2.exe",1) = 0 Then
    Msgbox(0,"Error","Programm is already running.")
    Exit
EndIf
EndFunc

When I lauch killwirelessv2.exe a second time, I get the message "Programm is already running".

But.. If I change the code like this, for example :

if _Singleton("Killwir.exe",1) = 0 Then

it is still working!

Why??

Tnanks.

Isn't that what you would expect ?

Maybe you can explain what it is you don't understand ?

[Tentaal]

Isn't that what you would expect ?

Maybe you can explain what it is you don't understand ?

What's the purpose of the string ($occurenceName) we must put between " "?

Help said

:

$occurrenceName string to identify the occurrence of the script .

Ok, but what is this occurence? Process name? exe name?

Edited November 11, 2006 by Tentaal

[Uten]

Use the source Luke...

_Singleton uses CreateMutex. So $occurenceName must be a unique identifier.

If lpName matches the name of an existing event, semaphore, waitable timer, job, or file-mapping object, the function fails and the GetLastError function returns ERROR_INVALID_HANDLE. This occurs because these objects share the same name space.