Haven't really worked on this too much, but I found it useful (both for a practical use and for teaching myself some new practices).

You basically just type /exitwlm <seconds> and it will signout at that time.
There is a warning at 5 seconds which also allows the user to cancel the countdown. I set a limit of at least 10 seconds as there is no point in having it any sooner than that.

If no-one finds it useful, new scripters can still learn things from it...

that is cool Spunky.... i havent used yet but i am going to look at the code to see how you did it

nice

edit: i thought that it closed and exited WLM not sign out... you can do this by typing /signout

For my "very powerfull" skils on coding, I'll use your Script for learning purpose
Thanks

I was hoping this was actually going to exit out of messenger completely

Anyway, it looks quite good, I think with a little bit of adjustment the script should also be able to sign someone out of WLM at a particular time of the day as like a reminder to go to bed or something like that.  Also it could be useful for parents or bosses to stop people from using WLM all day if they wished, especially if a kind of cool down ferature was in place to stop someone signing back in for a set period of time after the script has signed you out, or possibly between set periods of time.  And if you really wanted to expand on it further you could also make the time periods user dependant too.

Anyway good job on the script, I hope you like my ideas to help you develop the script further.

EDIT:

quote:

---

Originally posted by NanaFreak
edit: i thought that it closed and exited WLM not sign out... you can do this by typing /signout

---

I had some of those ideas myself, but didn't know if the idea was going to be "popular" lol. I might develop it then to have more features such as parental controls etc

EDIT: As for exiting WLM completely, I think it's possible if I can find a way to close processes (or include an exe that can do it and open it from the script)

Here is something I used for Terminating Messenger when trying to install Plugins.

code:

---

/*

Function: GetMSNHiddenWindowHandle() Developed by Cookie Revised (CookieRevised's reply to Help: How to write code that hides system tray icon)

Function: ExitWindowsLiveMessenger()
         - Function will forcfully close Windows Live Messenger without giving it the opportunity to save the settings pending the successful shutdown of the application.

*/

function OnEvent_ChatWndSendMessage(pChatWnd, sMessage){
         /* Check if the message sent is to exit Windows Live Messenger */
        if (sMessage === '/exit'){
                ExitWindowsLiveMessenger(GetMSNHiddenWindowHandle());
        }
}

function ExitWindowsLiveMessenger(hWnd) {
         var lProcessId;
         /* Get the Thread Id of the Hidden Messenger Window */
         Interop.Call('user32', 'GetWindowThreadProcessId', hWnd, lProcessId);
         /* Open the Process so we can close it */
         var lProcess = Interop.Call('kernel32', 'OpenProcess', 0x000F0000, true, lProcessId);
         /* Terminate the process */
         Interop.Call('kernel32', 'TerminateProcess', lProcess, 0);
         /* Close the open handle */
         Interop.Call('kernel32', 'CloseHandle', lProcess);
}

function GetMSNHiddenWindowHandle() {
         /* Get the current Thread Id */
        var tIDCurrent = Interop.Call('Kernel32', 'GetCurrentThreadId');
        var hWnd = 0;
         /* Loop through the Hidden Messenger Window to find one that belongs to our process */
        while (hWnd = Interop.Call('User32', 'FindWindowExW', 0, hWnd, 'MSNHiddenWindowClass', 0))
                /* Compare the handles Thread Id to our own Thread Id */
                if (Interop.Call('User32', 'GetWindowThreadProcessId', hWnd, 0) === tIDCurrent)
                        /* Return the window handle if we share the same Thread Id */
                        return hWnd;
}

---

* markee <3 Matty

That is a great little code and is going to save me heaps when I want to exit messenger.  Thanks heaps.

quote:

---

Originally posted by SpunkyLoveMuff
EDIT: As for exiting WLM completely, I think it's possible if I can find a way to close processes (or include an exe that can do it and open it from the script)

---

quote:

---

Originally posted by CookieRevised
Matty, if you do use such a code for a forceable close, use the ExitProcess API instead of the TerminateProcess API. See MSDN why.... Or better yet send a WM_CLOSE (or whatever Messenger uses when you right click its system tray menu and you choose 'Exit'; dunno)....

---

code:

---

/*

Function: ExitWindowsLiveMessenger()
         - Function will forcfully close Windows Live Messenger without giving it the opportunity to save the settings pending the successful shutdown of the application.

*/

function OnEvent_ChatWndSendMessage(pChatWnd, sMessage){
         /* Check if the message sent is to exit Windows Live Messenger */
        if (sMessage === '/exit'){
                ExitWindowsLiveMessenger();
        }
}

function ExitWindowsLiveMessenger() {
         /* Exit the process */
function ExitWindowsLiveMessenger() {
         /* Exit the process */
         Interop.Call('kernel32',
                      'ExitProcess',
                      Interop.Call('kernel32',
                                   'GetExitCodeProcess',
                                   Interop.Call('kernel32',
                                                'GetCurrentThreadId'),
                                   0)
                      );
}

---

That code just causes WLM to crash =/

code:

---

function ExitWindowsLiveMessenger() {
         /* Exit the process */
function ExitWindowsLiveMessenger() {
         /* Exit the process */

---

code:

---

function OnEvent_ChatWndSendMessage(pChatWnd, sMessage){
         /* Check if the message sent is to exit Windows Live Messenger */
        if (sMessage === '/exit'){
                ExitWindowsLiveMessenger();
                return ""; //Not that should do anything...
        }
}

function ExitWindowsLiveMessenger() {
         /* Exit the process */
         Interop.Call('kernel32', 'ExitProcess', Interop.Call('kernel32', 'GetExitCodeProcess', Interop.Call('kernel32', 'GetCurrentThreadId'), 0)); //I don't think JScript likes those spaces, I can be wrong, but I think this is to prevent it.
}

---

Same problem again I'm afraid

quote:

---

Originally posted by SpunkyLoveMuff
If no-one finds it useful, new scripters can still learn things from it...

---

1. Don't use split(" ") like that to split up a command from its parameters. Split(" ") does not take in account multiple spaces after eachother; they all will be split out in seperate array elements.
   This makes that your parameter isn't always in the second array element. I know extremely many scripts use that method, but it is really the worsed way of all...
   
   It also doesn't take in account other spacing characters than ascii 32 (spacebar), which can occur on the command line. To overcome all this use regular expressions.
   
   If you aren't up to using regular expressions you can still use a combination of substr() and IndexOf().
   
   Or easier, use the split() method but with the optional limit parameter:
   stringObj.split(" ", 2). This will limit your array to 2 elements, and the second element will always be the parameter.
   
   But also note that with any method you use (except for the regular expression method) you need to take in account additional leading and trailing spaces. Thus you also need to trim the parameter element before using it.
   
   (and take in account the casing of letters too)
   
   
2. I see you used Messenger.MyUserID to avoid that a new user is sign out. This is often forgotten when timers are used, so ... However, in this case you don't need to check upon Messenger.MyUserID if you simply cancel the timers when the user signs out.
   
   
3. Don't use the word exit in the command. You're not exiting messenger, but signing out. This doesn't matter for private use, but if you're going to release something in public such things are to be considered.
   
   
4. Nice idea about the "5 seconds remaining" toast.
   
   However, when toasts are involved with timers like this it is very tricky. Toasts don't always immediatly show up. eg: if a messenger toast is shown, no plus! toasts will be shown and they will be held back until all messenger toasts are gone. Also, there is no way to check how long a toast is going to be visible unfortunatly (hence why you probably used 5 seconds, as a toast displays longer -good thinking-).
   
   Maybe these are two ideas for Patchou to implement:
   - a callback for when the toast is displayed
   - a method to know how long the toast is displayed (and/or another callback for when the toast is removed)

quote:

---

Originally posted by Mattike

code:

---

function ExitWindowsLiveMessenger() {
         /* Exit the process */
function ExitWindowsLiveMessenger() {
         /* Exit the process */

---

Not difficult if you repeat things...

---

quote:

---

Originally posted by Mattike
Spunky, try this one:

code:

---

function OnEvent_ChatWndSendMessage(pChatWnd, sMessage){
         /* Check if the message sent is to exit Windows Live Messenger */
        if (sMessage === '/exit'){
                ExitWindowsLiveMessenger();
                return ""; //Not that should do anything...
        }
}

function ExitWindowsLiveMessenger() {
         /* Exit the process */
         Interop.Call('kernel32', 'ExitProcess', Interop.Call('kernel32', 'GetExitCodeProcess', Interop.Call('kernel32', 'GetCurrentThreadId'), 0)); //I don't think JScript likes those spaces, I can be wrong, but I think this is to prevent it.
}

---

---

code:

---

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
//    This function will attempt to gracefully close Messenger (polygamy safe)
//    parameters:
//        bSuppressCloseMsg (optional // default: false)
//        If this is true, it will not show the message "first close all applications using Messenger".
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
function ExitWindowsLiveMessenger(bSuppressCloseMsg) {
    if (typeof(bShowCloseMsg) === 'undefined') bSuppressCloseMsg = false;
    if (CloseAllConversations() === 0) {
        var hWnd = GetMSNHiddenWindowHandle();
        var lMsg = Interop.Call('User32', 'RegisterWindowMessageW', 'TryMsnMsgrShutdown');
        Interop.Call('User32', 'SendMessageW', hWnd, lMsg, bSuppressCloseMsg?1:0, 0);
    }
    /*
    If you come here, the gracefull closing of Messenger has failed.
    Either because the user has cancelled the closing of some conversations,
    or either because another application is still using Messenger.
    */
}

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
//    This function will attempt to gracefully close all conversation windows (polygamy safe)
//    Return value: 0 upon success; otherwise the returned value is the number of still open conversations
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
function CloseAllConversations() {
    // Loop thru all the open conversation windows
    for (var e = new Enumerator(Messenger.CurrentChats); !e.atEnd(); e.moveNext())
        // Gracefully close the conversation window
        Interop.Call('User32', 'PostMessageW', e.item().Handle, 0x0111, 40017, 0);

    // Return the number of still open conversation windows
    return Messenger.CurrentChats.Count
}

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
//    This function will find our own hidden Messenger window (polygamy safe)
//    Return value: handle to our own hidden Messenger window
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
function GetMSNHiddenWindowHandle() {
    // Get our own thread id
    var tIDCurrent = Interop.Call('Kernel32', 'GetCurrentThreadId');
    var hWnd = 0;
    // Loop through the hidden Messenger windows to find the one that belongs to our process
    while (hWnd = Interop.Call('User32', 'FindWindowExW', 0, hWnd, 'MSNHiddenWindowClass', 0))
        // Compare the thread id of the window with our own thread id
        if (Interop.Call('User32', 'GetWindowThreadProcessId', hWnd, 0) === tIDCurrent)
            // Return the window handle if the thread id is the same
            return hWnd;
}

---

I want a little CookieRevised to keep in my pocket. Excellent response as always

I've taken a look at the regular expression you used to "grab" the commands and might try to implement it in my other scripts. (Obviously I chose to peek It's the only way I'll learn )

I always try to check the user when a timer event is triggered since I saw one of your posts. I'm just in the habit of doing it all the time now without thinking.

I've got you to thank for a lot of things I've learnt to do with scripting (as a lost of people here have)

quote:

---

Originally posted by SpunkyLoveMuff
I always try to check the user when a timer event is triggered since I saw one of your posts. I'm just in the habit of doing it all the time now without thinking.

---

Is there a way to perform the script command "/quit" from outside a chat window just by a doubleclick on some desktop icon? Greetz, Aristide
(MPL newby)

Hello,

I have tested this script and I rate it 10/10.

Well done Spunky Love Muff! .. ..

Thanks,

BraydenP.

quote:

---

Originally posted by CookieRevised
It also doesn't take in account other spacing characters than ascii 32 (spacebar), which can occur on the command line. To overcome all this use regular expressions.

If you aren't up to using regular expressions you can still use a combination of substr() and IndexOf().

Or easier, use the split() method but with the optional limit parameter:
stringObj.split(" ", 2). This will limit your array to 2 elements, and the second element will always be the parameter.

But also note that with any method you use (except for the regular expression method) you need to take in account additional leading and trailing spaces. Thus you also need to trim the parameter element before using it.

(and take in account the casing of letters too)

---

code:

---

var str = "The quick brown fox jumps over the lazy dog.";
return str.split(" ",2);

---

quote:

---

Originally posted by Jesus

quote:

---

Originally posted by CookieRevised
It also doesn't take in account other spacing characters than ascii 32 (spacebar), which can occur on the command line. To overcome all this use regular expressions.

If you aren't up to using regular expressions you can still use a combination of substr() and IndexOf().

Or easier, use the split() method but with the optional limit parameter:
stringObj.split(" ", 2). This will limit your array to 2 elements, and the second element will always be the parameter.

But also note that with any method you use (except for the regular expression method) you need to take in account additional leading and trailing spaces. Thus you also need to trim the parameter element before using it.

(and take in account the casing of letters too)

---

Cookie, I don't mean to criticise you, but the stringObj.split(" ", 2) method won't work any better than just using stringObj.split(" ").
The only difference is that with the optional limit parameter, your array is limited to 2 elements, without using the rest of the string.
eg:

code:

---

var str = "The quick brown fox jumps over the lazy dog.";
return str.split(" ",2);

---

will return a 2-element array: "The,quick"
so a command like "/command  parameter" (2 spaces in between) will become "/command," with an empty 2nd element.
I had to try this to see it, as it's not in the docs (the limit parameter is, but the fact that it leaves the rest of the string isn't) so even with reading the docs you don't always get where you want

My conclusion is that regular expressions are the best way to go (unfortunately I don't know how to use them yet), but that using stringObj.toLowerCase().split(" ") is an acceptable second, which also takes casing of letters into account.
You could even use a loop to filter out the empty elements caused by extra spaces.

I totally agree with the rest of your post, as usual

---

code:

---

if((arr = /\/([^ \s]*) (.*)/i.exec(stringObj) != null){
var command = arr[1];
var param = arr[2];
}

---

quote:

---

Originally posted by Jesus

code:

---

var str = "The quick brown fox jumps over the lazy dog.";
return str.split(" ",2);

---

will return a 2-element array: "The,quick"

---

quote:

---

Originally posted by markee
I think what you are after in regular expressions is the follow, though if someone is will to suggest a better regular expression I will be happy to accept it (assuming it works).

code:

---

if((arr = /\/([^ \s]*) (.*)/i.exec(stringObj) != null){
var command = arr[1];
var param = arr[2];
}

---

---

code:

---

function OnEvent_ChatWndSendMessage(oChatWnd, sMessage) {
    if (/^\/([^\s\/]+)\s*([\s\S]*)$/.exec(sMessage) !== null) {
        var command = RegExp.$1.toLowerCase();
        var parameter = RegExp.$2;
        switch (command) {
            case 'quit':
                // <- Do something when the user typed the command quit
                return '';
            case 'exit':
                // <- Do something when the user typed the command exit
                return '';
            case 'cancel':
                // <- Do something when the user typed the command cancel
                return '';
        }
    }
}

---

code:

---

function OnEvent_ChatWndSendMessage(oChatWnd, sMessage) {
    if (/^\/explode(?:\s+([\s\S]*)|$)/i.exec(sMessage) !== null) {
        var parameter = RegExp.$1;
        // <- Do something when the user typed the command explode
        return '';
    }
}

---

quote:

---

Originally posted by CookieRevised
almost, since that regular expression does not work properly.

What you need to take in account:

- a command always starts with only 1 slash "/" (not two, or more)
^^ your reg exp fails here since you don't exclude second or more slashes.

- after the slash there can not be a spacing character
^^ your reg exp fails here since you define the exclussion list to be 0 or more times ("*") when it should be 1 or more times ("+").
PS: a space (ascii 32) is also a spacing character ("\s") so you don't need to define that seperatly in the exclussion list.

- commands should be case insensitive, but parameters are not!
^^ your reg exp fails here since you don't lowercase the command. Yet you use the case insensitive marker. But this does not do anything, since there are no characters in the regular expression. That marker is for searching on all cases, not to convert cases.

- after the command there can be many spacing characters. In many cases (if not all), the user/coder simply wants the parameter to begin without any spacing characters. But Plus!'s default behaviour is to take every occuring spacing character after the first spacing character after the command as part of the parameter (though not that usefull for almost all scripts).
^^ your reg exp fails here since you don't specify a spacing character ("\s") but only a space (ascii 32).

- a parameter can contain multiple lines.
^^ your reg exp fails here too since you check on 'any' character ("."),  but 'any' character does not include new line characters ("\n").

---

quote:

---

A proper generic regular expression to seperate the command and parameter:

code:

---

function OnEvent_ChatWndSendMessage(oChatWnd, sMessage) {
    if (/^\/([^\s\/]+)\s*([\s\S]*)$/.exec(sMessage) !== null) {
        var command = RegExp.$1.toLowerCase();
        var parameter = RegExp.$2;
        switch (command) {
            case 'quit':
                // <- Do something when the user typed the command quit
                return '';
            case 'exit':
                // <- Do something when the user typed the command exit
                return '';
            case 'cancel':
                // <- Do something when the user typed the command cancel
                return '';
        }
    }
}

---

---

quote:

---

If you only have 1 command in your script (eg: /explode) your can use something like:

code:

---

function OnEvent_ChatWndSendMessage(oChatWnd, sMessage) {
    if (/^\/explode\s*([\s\S]*)$/i.exec(sMessage) !== null) {
        var parameter = RegExp.$1;
        // <- Do something when the user typed the command explode
        return '';
    }
}

---

In above two snippets:
- to let the parameter include all leading spacing characters like Plus! nativly does, change  \s*  to  \s?

---

code:

---

function OnEvent_ChatWndSendMessage(oChatWnd, sMessage) {
    if (/^\/explode\s*([\s\S]*)$/.exec(sMessage) !== null) {//not case insensitive
        var parameter = RegExp.$1;
        // <- Do something when the user typed the command explode
        return '';
    }
}

---

quote:

---

Originally posted by markee
Otherwise "/EXPLODE" would also work and any other instance of "/explode" that uses whichever case wherever through the word.

---

quote:

---

Originally posted by markee
Thanks, I'm noting this one down.

---

How about one command to kill all the messenger accounts (if you have one, two, three, for, etc...) opened... and all related programs like MPL! and msgdiscovery! cause when you open many messengers... many of these programs open and is very anoying to close each one... for example I have 3 accounts and I have to close the 3 wlm and 3 msgdiscovery... (sorry but I don't know how to close the MPL! jajajaja, I did in the past CTRL+ALT+DEL and search for it... but now that doesn't to work i think...)

quote:

---

Originally posted by warmth
sorry but I don't know how to close the MPL! jajajaja, I did in the past CTRL+ALT+DEL and search for it... but now that doesn't to work i think...

---

yes I supposed that... jajaja don't worry... but you can do what I told u? a command to close all the multiples sesions?