Jump to content
Sign in to follow this  
DasBo

_Singleton() not working with v3.2.12.0 ?

Recommended Posts

DasBo

While migrating one of my tools to autoit version 3.2.12.0 I found that the _singleton() function doesn't work anymore. I can reproduce this even with the minimum example from the help file. The function seems to return 0 either if the application is started for the first time or if another instance is already running. With version 3.2.10.0 singleton works fine on the same machine.

Can you confirm this or am I the only one with this problem?

I'm using AutoIt on Vista SP1. The problem occurs with compiled and non-compiled scripts.

Share this post


Link to post
Share on other sites
ReaImDown

While migrating one of my tools to autoit version 3.2.12.0 I found that the _singleton() function doesn't work anymore. I can reproduce this even with the minimum example from the help file. The function seems to return 0 either if the application is started for the first time or if another instance is already running. With version 3.2.10.0 singleton works fine on the same machine.

Can you confirm this or am I the only one with this problem?

I'm using AutoIt on Vista SP1. The problem occurs with compiled and non-compiled scripts.

your problem is solved here.... http://www.autoitscript.com/forum/index.php?showtopic=37289 ...last post.


[u][font="Century Gothic"]~я α и d γ ĵ . ċ . ѕ қ ϊ и и ε я~- My Programs -auto shutdownSleep funcdisallow programs[/font][/u]

Share this post


Link to post
Share on other sites
SadBunny

/edit - sorry, thanks for answering question and urge me to read FAQ more often :)

Edited by SadBunny

Roses are FF0000, violets are 0000FF... All my base are belong to you.

Share this post


Link to post
Share on other sites
ReaImDown

same solution work?

Edited by ReaImDown

[u][font="Century Gothic"]~я α и d γ ĵ . ċ . ѕ қ ϊ и и ε я~- My Programs -auto shutdownSleep funcdisallow programs[/font][/u]

Share this post


Link to post
Share on other sites
SadBunny

same solution work?

Actually, no! The _Singleton("test\test",1) always returns 0 even if it is the first run (but it should say "the first occurence of test is running").


Roses are FF0000, violets are 0000FF... All my base are belong to you.

Share this post


Link to post
Share on other sites
ReaImDown

Actually, no! The _Singleton("test\test",1) always returns 0 even if it is the first run (but it should say "the first occurence of test is running").

...try it again.... this works 4 me (remember the script needs to be compiled.)

If _MutexExists("test.exe") Then
; We know the script is already running. Let the user know.
    MsgBox(0, "Script Name", "This script is already running. Using multiple copies of this script at the same breaks the [(UltimaCoder)] License!")
    Exit
EndIf

Func _MutexExists($sOccurenceName)
    Local $ERROR_ALREADY_EXISTS = 183, $handle, $lastError
    
    $sOccurenceName = StringReplace($sOccurenceName, "\", ""); to avoid error
    $handle = DllCall("kernel32.dll", "int", "CreateMutex", "int", 0, "long", 1, "str", $sOccurenceName)

    $lastError = DllCall("kernel32.dll", "int", "GetLastError")
    Return $lastError[0] = $ERROR_ALREADY_EXISTS
    
EndFunc ;==>_MutexExists

while 1
    sleep(100)
WEnd

[u][font="Century Gothic"]~я α и d γ ĵ . ċ . ѕ қ ϊ и и ε я~- My Programs -auto shutdownSleep funcdisallow programs[/font][/u]

Share this post


Link to post
Share on other sites
SadBunny

Yes, that works. Must be something different in what you did and what misc.au3 does... ?

Does the helpfile example work for you?


Roses are FF0000, violets are 0000FF... All my base are belong to you.

Share this post


Link to post
Share on other sites
SadBunny

Yes, that works. Must be something different in what you did and what misc.au3 does... ?

Does the helpfile example work for you?

Figured it out (stupid I didn't see that earlier): seems that helpfile script was only tested when making, and not after placing in helpfile structure :) When you rename the _Singleton.au3 (which is opened when you 'open this script' from the helpfile) to test.au3 manually, then it works :P


Roses are FF0000, violets are 0000FF... All my base are belong to you.

Share this post


Link to post
Share on other sites
ReaImDown

Yes, that works. Must be something different in what you did and what misc.au3 does... ?

Does the helpfile example work for you?

yes actually...just dont use test/test haha

#include "Misc.au3"
if _Singleton(@ScriptName,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")

[u][font="Century Gothic"]~я α и d γ ĵ . ċ . ѕ қ ϊ и и ε я~- My Programs -auto shutdownSleep funcdisallow programs[/font][/u]

Share this post


Link to post
Share on other sites
DasBo

your problem is solved here.... http://www.autoitscript.com/forum/index.php?showtopic=37289 ...last post.

Thanks for the tip. _MutexExists() works.

But is there a reason, why _Singleton() doesn't work anymore with the new AutoIt version? At least not in the same way as in versions before 3.2.12.0?

Share this post


Link to post
Share on other sites
PsaltyDS

Thanks for the tip. _MutexExists() works.

But is there a reason, why _Singleton() doesn't work anymore with the new AutoIt version? At least not in the same way as in versions before 3.2.12.0?

You haven't posted any code yet to indicate what doesn't work for you. The example in the help file is bad, as indicated earlier:
#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")

The $sOccurenceName = "test\test" was a bad example as it attempts to use an invalid name space. If you simply replace that with "MyUniqueScriptIdString", or some such, it will work as advertised.

If your problem is not with the example script, please post a short script to demonstrate what doesn't work for you, in particular what kind of ID string you chose.

:)


Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law

Share this post


Link to post
Share on other sites
DasBo

The $sOccurenceName = "test\test" was a bad example as it attempts to use an invalid name space. If you simply replace that with "MyUniqueScriptIdString", or some such, it will work as advertised.

If your problem is not with the example script, please post a short script to demonstrate what doesn't work for you, in particular what kind of ID string you chose.

:P

Yes, I tried with the unchanged help file example. I didn't notice, that this is related to name spaces. Without backslashes it works now.

BTW: Is there any complete :P documentation of compatibility breaking changes from version 3.2.10.x to 3.2.12.0? I have no problems with function names changing, because syntax errors can be found easily. But changing order and function/meaning of arguments is a real pain without documentation. How can I ever be sure, that my tools don't produce runtime errors with the new version? :)

Share this post


Link to post
Share on other sites
DaveF

BTW: Is there any complete :P documentation of compatibility breaking changes from version 3.2.10.x to 3.2.12.0?

If you'll go to the AutoIt3 help file, top of the Contents, History/Changelog, and click the 'script-breaking changes' link you'll see what the developers anticipated might cause problems with existing scripts.

How can I ever be sure, that my tools don't produce runtime errors with the new version? :)

You can compile your scripts using versions of the AutoIt binaries that were known-good when the script was designed, and/or you can have a test environment for your scripts to try new versions of the AutoIt binaries before adopting them.

AutoIt is great in part because it's a non-invasive all-in-one tool, but it isn't exempt from the Best Practices that one would use for any other software product.


Yes yes yes, there it was. Youth must go, ah yes. But youth is only being in a way like it might be an animal. No, it is not just being an animal so much as being like one of these malenky toys you viddy being sold in the streets, like little chellovecks made out of tin and with a spring inside and then a winding handle on the outside and you wind it up grrr grrr grrr and off it itties, like walking, O my brothers. But it itties in a straight line and bangs straight into things bang bang and it cannot help what it is doing. Being young is like being like one of these malenky machines.

Share this post


Link to post
Share on other sites
DasBo

If you'll go to the AutoIt3 help file, top of the Contents, History/Changelog, and click the 'script-breaking changes' link you'll see what the developers anticipated might cause problems with existing scripts.

You can compile your scripts using versions of the AutoIt binaries that were known-good when the script was designed, and/or you can have a test environment for your scripts to try new versions of the AutoIt binaries before adopting them.

AutoIt is great in part because it's a non-invasive all-in-one tool, but it isn't exempt from the Best Practices that one would use for any other software product.

Of course I read the warning on top of the change log. Scanning all my scripts for the mentioned functions and keywords was the easy part... :P After that I tried to compile the scripts and solved all the syntax errors for changed GUI function names. That was kind of easy too. But the real annoying part came, when I realized that the order of arguments for several functions changed and sometimes even the meaning of arguments. This was no fun at all, because after installing the new version, the old help files were gone too and I couldn't easily compare old and new syntax.

Until now, I'm not sure, if there are any "time bombs" left in my bigger scripts like the change of interpretation of the _Singleton() argument, that is documented nowhere in the change log. I hope, there will be no further of these (undocumented) compatibility breaking changes in the autoit language for the next few years... :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×