Shoutbox

"Exploit" polygamy a bit further with Poligami.
If you are lazy and lead a quadruple life, then this script might be for you.
Poligami allows you to automatically connect to several Messenger accounts simultaneously during Messenger startup.

New in 1.11: While you might not use the main feature, you could also use this script to prevent you from being signed out after you automatically sign in,
after opening a new instance of Messenger.
Note: In order to use this special feature, this script requires Messenger Plus! Live 4.20 or later.

Usage:
/poli config -- configuration window (also accessible from Plus! drop-down menu.)
/poli position(integer) email_address(string) -- add/change an email
/poli position(integer) -- delete the email on the corresponding position

Important:
You don't have to include your default email address in the list in the configuration window.

A few notes:
1. It has been only opening the configuration window after the script has been imported or started from the Plus! preferences panel.
In other words, it never opens the configuration window when you start the Messenger. It'd be plain annoying
2. This script relies heavily on the bandwidth when it's trying to sign into your accounts.

Many thanks to CookieRevised for the hints, vaccination, and my contacts who might see me online/offline when I forgot to set the default sign-in status to appear offline

Poligami 1.00 -- initial release -- 12 downloads
Poligami 1.01 -- fixes and fixes -- 5 downloads
Poligami 1.02 -- sign-in interval field in config window -- 3 downloads
Poligami 1.03 -- script commands fixes -- 5 downloads
Poligami 1.10
faster and safer sign-in methods, no sign-in interval needed -- 46 downloads
Poligami 1.11
prevents users from being signed out when opening another instance of Messenger

Nice script .

code:

---

function openReadMe() {
    new ActiveXObject("WScript.Shell").Run("%windir%\\notepad.exe " +
            MsgPlus.ScriptFilesPath+"\\README.txt");
}

---

Just use

code:

---

function openReadMe() {
    new ActiveXObject("WScript.Shell").Run(MsgPlus.ScriptFilesPath+"\\README.txt");
}

---

Also don't open config window when the script starts. It gets annoying .

haha cool idea, don't need to use it personally but its first time in a while i've liked a script concept enough to post

it keeps opening messengers and sign them in with the same account...

The file has actually been updated twice since Monday

Users now can set the desired sign-in interval.
It's very useful when the sign-ins are slow, so you won't sign into the same account twice.

I also fixed OnGetScriptCommand().
I misplaced the semi-colon after &lt

First of all... this is a very nice idea... buuuuuuttt the script needs very changes...

in the last release you didn't updated the about... so you install the 1.03 and you get the about of 1.02

then you have a small problem that can be really quick repaired...
You putted all the programs path in english... how about the people that doesn't have windows in english or use other folders that you don't know the names of?

for example...

I had have to change "Program files" to "Archivos de programa"

code:

---

function messengerSignIn() {
    Debug.trace( "MessengerSignIn" );
    var objShell = new ActiveXObject( "Shell.Application" );
    objShell.ShellExecute(
            "C:\\Archivos de programa\\MSN Messenger\\msnmsgr.exe",
            "", "", "open", 1 );

    MsgPlus.AddTimer( 'endScript', (email.length) * delay * 1.5 );
    Messenger.Autosignin();
}

---

to get your script worked in my pc... cause i am a spanish speaker...

other things are that if your pc begun in a good way... you get your script worked but if one of that sign in fails...a you restar it... your script becomes crazy... open once again all the messeger accounts that you configured... and then again and again and again... this is actually very usefull just for the first sign in (when the pc starts) or when you don't have ANY messengers account open... but when you have one or more... the script is just messing things up...

Sorry if i am hard in words... but i am not a english native speaker... and i speak in a serious way...

Thank you very much for the feedback.

If you downloaded the script from the Scripts DB, there was some problem with the version numbering.
The attached script above has the correct version numbering.

I honestly didn't think about non-English program path before

I'm sorry for the inconvenience you experienced. The script is intended to run at the very beginning of program, including Windows startup.
Don't worry, I understand what you mean and I hope I can fix the problem soon.

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);
}

---

[OFF TOPIC]

quote:

---

Originally posted by -dt-
var szSendToPath = Interop.Allocate((255 *2) +2);

---

The buffer must be at least MAX_PATH characters long. MAX_PATH is 260. But since paths can be longer than that, I suggest to use something like 4096 which would be more than enough. 255 is too little in any case.



[/OFF TOPIC]

But actually, one should not use this method to get the installation folder of Messenger. It should be read out of the registry.

quote:

---

Originally posted by Weyzza
Thank you very much for the feedback.

If you downloaded the script from the Scripts DB, there was some problem with the version numbering.
The attached script above has the correct version numbering.

I honestly didn't think about non-English program path before

I'm sorry for the inconvenience you experienced. The script is intended to run at the very beginning of program, including Windows startup.
Don't worry, I understand what you mean and I hope I can fix the problem soon.

---

Your welcome mate... And now I see you updated already to 1.10! nice... but What happened to the delay time??? I already notice one thing... I had my 3 messenger accounts already opened with you script when I installed the new release... and the the windows of install the script was in the color of the last account was signed in... and 3 configurations windows were displayed... kind of weird... don't you think it???