Shoutbox

why arent there any Messneger.Open and .Close methods ???

edit
to open/close the contaclt list window as they are in the MessengerAPI com...

quote:

---

Originally posted by MX-G
Because those methods arent 100% reliable
ex: when a contact minimize your Window Chat those methods tell you than he or she closed your window

---

To be blunt your post is way off. Thanks for coming out.

Taz means why isn't there an option within the Messenger object to Open or Close the Contact List.

Taz to be honest with you I was actually wondering the same thing. This would make your Windows Management Plugin so much easier. My suggestion would be to use the ShowWindow API and hide the window (SW_HIDE) and then show it (SW_SHOW) when needed, that is the only work around available for now until Patchou incorporates those if he does.

quote:

---

Originally posted by Matty
Taz means why isn't there an option within the Messenger object to Open or Close the Contact List.

Taz to be honest with you I was actually wondering the same thing. This would make your Windows Management Plugin so much easier. My suggestion would be to use the ShowWindow API and hide the window (SW_HIDE) and then show it (SW_SHOW) when needed, that is the only work around available for now until Patchou incorporates those if he does.

---

The contact list is destroyed and re-created that is why the memory load hits the charts only when the contaclt list is open..
so SW_HIDE and SW_SHOW are useless if the contacltlist is closed initially and the fact that unnessecary memory load is reserved...

This uses the messenger api (as opening/closing is a function in it):

To open it:

code:

---

var MessengerAPI = new ActiveXObject('Messenger.UIAutomation.1');
var MessengerWnd = MessengerAPI.IMessengerWindow;
MessengerWnd = MessengerAPI.Window;
MessengerWnd.Show();

---

To close it:

code:

---

var MessengerAPI = new ActiveXObject('Messenger.UIAutomation.1');
var MessengerWnd = MessengerAPI.IMessengerWindow;
MessengerWnd = MessengerAPI.Window;
MessengerWnd.Close();

---

To toggle it (Window.IsClosed is a boolean that says if its closed or not ):

code:

---

var MessengerAPI = new ActiveXObject('Messenger.UIAutomation.1');
var MessengerWnd = MessengerAPI.IMessengerWindow;
MessengerWnd = MessengerAPI.Window;
if(MessengerWnd.IsClosed == true){
MessengerWnd.Show();
} else {
MessengerWnd.Close();
}

---

quote:

---

Originally posted by deAd
This uses the messenger api (as opening/closing is a function in it):

To open it:

code:

---

var MessengerAPI = new ActiveXObject('Messenger.UIAutomation.1');
var MessengerWnd = MessengerAPI.IMessengerWindow;
MessengerWnd = MessengerAPI.Window;
MessengerWnd.Show();

---

To close it:

code:

---

var MessengerAPI = new ActiveXObject('Messenger.UIAutomation.1');
var MessengerWnd = MessengerAPI.IMessengerWindow;
MessengerWnd = MessengerAPI.Window;
MessengerWnd.Close();

---

To toggle it (Window.IsClosed is a boolean that says if its closed or not ):

code:

---

var MessengerAPI = new ActiveXObject('Messenger.UIAutomation.1');
var MessengerWnd = MessengerAPI.IMessengerWindow;
MessengerWnd = MessengerAPI.Window;
if(MessengerWnd.IsClosed == true){
MessengerWnd.Show();
} else {
MessengerWnd.Close();
}

---

---

Ya you ever look at your processes before you run the code and afterwards? By using the Windows Messenger API you are causing Windows Messenger to run.

yeah i already thought of that and it has the implication Matty said, Window Messanger is required and runs automatically in a hidden state...

Really? *looks at processes* I'm not seeing it what's the process name?

Also, if you declare it once in initialize, then delete it on uninitialize, its fine :/ but I've never had any problems with it at all..

quote:

---

Originally posted by deAd
Really? *looks at processes* I'm not seeing it what's the process name?

Also, if you declare it once in initialize, then delete it on uninitialize, its fine :/ but I've never had any problems with it at all..

---

msmsgs.exe

No once the processes is launched it stays no matter if it is removed. The process has to be ended manually.

, after i closed it manually, it didnt come back again. but the API was working fine.

So i guess no-one else is interested in the API method...
Tooo bad...