Shoutbox

I'm trying to destroy a window through the API (plus doesn't offer functions to do this), but either instantly or soner or later WLM crashes ...

I can hide/show windows, close them (this doesn't destroy them, just sorta minimizes them) and everything works fine.

code:

---

Hiding:
Interop.Call('user32','ShowWindow',Wnd.Handle, 0);

Showing:
Interop.Call('user32','ShowWindow',Wnd.Handle, 1);

Close(minimize):
Interop.Call('user32','CloseWindow',Wnd.Handle);

Destroy:
Interop.Call('user32','DestroyWindow',Wnd.Handle);

---

According to MSDN this is correct ...

Any ideas ?

Thanks

Er...I do see "Close" method in PlusWnd Object, in the scripting documentation

quote:

---

Originally posted by Mnjul
Er...I do see "Close" method in PlusWnd Object, in the scripting documentation

---

I don't think he wants to destroy a PlusWnd object, but I think he wants to destroy a window, other a window created by his script

The PlusWnd::Close function destroys the window.

Syntax

code:

---

Close(
    [number] ExitCode
);

---

Parameters
ExitCode
[number] A number specifying the exit code for the window. It has no particular meaning for Messenger Plus! and can be anything the script's developer wishes it to be.

If you want to close a window that isn't created by your script, then the correct way would be to send it a WM_CLOSE message.
This lets it tidy up, and do anything it needs to before closing, however is you destroy the window straight away, it can't finish what it was doing, and quite often causes some crashing.

Yeah I should have said that it's not a PlusWnd that I want closed, but a conversation window one Sorry 'bout that.

@ Plik: Thanks I'm gonna try it

Try:

code:

---

Interop.Call("User32", "SendMessageW", Wnd.Handle, 0x10, 0, 0);

---

0x10 is WM_CLOSE.

If that doesn't work then try SendMessage instead of SendMessageW.

Sometimes even this method crashes WLM though, but I'm not sure why. It should make the window do exactly what would happen if you pressed the X button.

I couldn't use WM_CLOSE directly (didn't work here), but I found this workaround that is working as expected:

code:

---

Interop.Call('user32','SendMessageW',wnd.Handle, 0x0112, 0xF060, 0)

---

0x0112 for system command
0xF060 for close

Thanks all

Even that last one crashes wlm...
Try using PostMessageW, instead of SendMessageW.
This will, unlike SendMessageW, not wait for the message to be processed, don't ask me why it works, but it does...