Shoutbox

Do you have 3 Messenger opened when importing the script?
I think when a script is imported, it'll be initialized to every Messenger.
I'm not sure about this, though, but I'm guessing that's why it's behaving that way.

I don't think I need the delay time anymore, since it has a better sign-in method.

Thank you for your support

yes actually I obviously know that is that! jajajaja I was just kidding... I was trying to telling u... that if you can do in anyway  that only one config windows appear... (maybe the first one...) no 3...

Your welcome... I am helping u... because is the first script that I actually USE ALWAYS! I didn't request it... but I got it like ring in finger... jajajaja

Ah yeah... unfortunately, scripts have some limitations in detecting some things.

Please let me know if you find any problem

Ok mate... I will... thanks for you patience! jajajaja

I proved most of the things of the new version of your script and you did a nice job... but how about when you close all your messenger accounts? You can't do that the multiple messenger start over again, in the way I already explain it to you mate???

Hello

First thanks a lot for this plug-in it's very usefull !!! 10000 thanks lol

(i have 4 msn account)

i notice just one little bug... when we use the plug

every thing is okay but when i have an internet disconnection (like u know msn reconnect automatically...) when msn is reconnecting the plug-in open again my 4 msn (not 3 like habitually but 4) so when i let him totaly reconnect alone at last i have 8 msn opned (4 connected and 4 disconnected)

can u do some thing please to make it better please please lol

i guess you can disable the plug after the first work and enable it on msn closure...

or detect if the account is connected before opning a new msn

or detecting how many msn is running

or make a little button next live button on msn window to enable/disable the plug easily

or simply detect an internet disconnection to enable/disable the plug

or detect an msn disconnection to enable/disable

or disable the autologin of secondarys acounts after connecting them. (i think it's the better thing to do)

thanks a lot... if i know programming live plus plug i will done it but there is much to know... lol

Thank you for using this script.

You have many wonderful ideas on how to solve the bug, but sadly, there are some limitations that Plus! has that make the script imperfect.

Let me try to answer your ideas:
#1 i guess you can disable the plug after the first work and enable it on msn closure...
I originally thought of this when I started to write the script, but usability was the problem. When the script is inactive, users won't be able to add new email addresses. In order to access the configuration window, the script must be running.

or detect if the account is connected before opning a new msn
I thought of this one, too. But unfortunately there's no way to do that.

#3 or detecting how many msn is running
Right now, there's no way to know how many Messengers are running.
I tried that approach by counting the number of Messengers that have been started or ended, but there was another problem.
When the computer is shutdown, Plus! will also be shutdown and currently there is no way for Plus! to detect that a Messenger instance is ended.
This script depends on the events that Plus! detects.
For example, when a user signs in or signs out, exits Messenger.

or make a little button next live button on msn window to enable/disable the plug easily
Plus! doesn't allow us to do it

or simply detect an internet disconnection to enable/disable the plug
Same reason like #1

or detect an msn disconnection to enable/disable
Same reason like #1

or disable the autologin of secondarys acounts after connecting them. (i think it's the better thing to do)
Same reason like #3
I tried that as well, but since I cannot detect the case where the computer is shut down, the auto-signin would break and the script would not run at all

---

To all people, can you tell me how to detect an event in which the computer is being shutdown?

The problem intika experiences is/was something I warned about (at least I thought... dunno for certain) for such scripts. However it is perfectly possible to make the script so that it does not open new instances anymore in those cases. It takes clever planning of how the script works though and it isn't that easy/straightforward...





EDIT: fixed some spelling

Hello Weyzza thanks for your answer

i thought about it lol it appear more difficult to do that...

so...

what do u think if you create 2 diffrent plug one to add emails etc. (in the registry) this one will be alway active (enabled).
and an other to make the polygami this one will be disabled after the poligami work...

the first one will be called for example "poli-interface" and the second "poli-work"

------------------------------------

So poli-work will auto disable himself after work and poli-interface will be there to add or remove emails

Or the poli-interface will disable the poli-work after poligamy work

Or poli-interface will disable the poli-work if the statut of msn is 0  unknown (Messenger::MyStatus) like when msn is disconnected...

And/Or Poli-interface will enable poli-work if the work is not done

And/Or Poli-interface will disable poli-work if one of the adress that ar in the list is triying to connect after work

or some other idea looool

---------------------------------------

this will be easy to do ! ?


what do u think ?

quote:

---

Originally posted by intika
what do u think if you create 2 diffrent plug one to add emails etc. (in the registry) this one will be alway active (enabled).
and an other to make the polygami this one will be disabled after the poligami work...

---

You don't need 2 scripts at all. In fact, it will make this whole script even more confusing, prone to errors, etc... It really will not fix anything at all.

The script can be active all the time, that's not the problem.

The problem is the event on which the script does what it does. This should be tweaked much better and in some cases the script should not open new instances. That doesn't mean the script should be disabled, that means the script should use some checks and/or track in a proper what is running.

eg: when a new messenger instance starts, all scripts under that instance will be started again too. Thus this means that this poligami script is actually run more than once, each time in another instance. This fact must be exploited to make this script work properly.

quote:

---

Originally posted by -dt-

quote:

---

Originally posted by Weyzza
I honestly didn't think about non-English program path before (Smilie)

---

you can use SHGetSpecialPath for that, you should never assume the path.

code:

---

var CSIDL_PROGRAM_FILES = 0x0026;

Debug.Trace("Program Files path: " + getSpecialFolder(CSIDL_PROGRAM_FILES))

function getSpecialFolder(CSIDL){
    var szSendToPath = Interop.Allocate((255 *2) +2);
    Interop.Call("Shell32", "SHGetSpecialFolderPathW", 0, szSendToPath, CSIDL, 0);
    return szSendToPath.ReadString(0);
}

---

---

You shouldn't assume Messenger is installed in Program Files