Hi all,

I wrote a small script which should prevent me from closing a chat just after receiving a message (like in aMSN), but so far I've only managed to show a toast with the contact's name and message when I close the chat too fast.

My question is: Is there a way to stop a chat window from closing?

Another option is to reopen the chat immediately, but I don't know if it's possible to show the conversation after the window has been closed.

I know how to do this, but it requires a DLL and a keyboard hook.

hmm I've never done that... is it hard to do?

Not massively really. If you like, I can post some code later today for you to look at.

quote:

---

Originally posted by RaceProUK
I know how to do this, but it requires a DLL and a keyboard hook.

---

quote:

---

Originally posted by RaceProUK
Not massively really. If you like, I can post some code later today for you to look at.

---

quote:

---

Originally posted by CookieRevised

quote:

---

Originally posted by RaceProUK
I know how to do this, but it requires a DLL and a keyboard hook.

---

to intercept ALT-F4... But what about all the other ways you can close a chat? Isn't it better to hook the window and intercept the close window message?

---

A better way would be to intercept the actual windows API message that closes the window (WM_CLOSE, or something like that; Use a program like MessageSpy++ to find out).

Edit:
Coding in Windows API is not that hard to do, and if you're fluent in another natively compilable language (Like Delphi or C++), you could probably create a DLL that wraps all the API code you need, and simplify your script's code and operation by getting the DLL to handle all the messy stuff.

I have effectively used WM_NCACTIVATE to detect a flash event to any window, all you need to figure out is how to detect and cancel out that API message and you've practically covered all your bases in terms of closing conversation windows.

You'll need to get your hands dirty in Windows API to be able to use this effectively, but well worth it and rewarding.

Hope that helps.

Well I'm not afraid to (try to) learn something, so I'll take a look at it.

quote:

---

Originally posted by Jesus
Well I'm not afraid to (try to) learn something, so I'll take a look at it.

---

Am I right that dscwpmsg.dll from this thread can do what I want?
I've tried some stuff with it, but I can't figure out what does and does not work

*bump*

anyone?

It would be better if you looked for the API message that closes the window (Most likely WM_NCCLOSE) and cancel it out.

That would be your best bet, as nothing would be able to close the window while your script intercepts and terminates this message.

I grabbed this from a Delphi forum, which you could probably use in a DLL and call the function from your script. Take note of the bolded pieces of code.

code:

---

procedure TForm1.FormCloseQuery(Sender: TObject; var CanClose: Boolean);
var
answer : string;
begin
answer := InputBox('Admin password?','password', '');
if answer='yourpassword' then canclose:=true
else
canclose:=false;
end;

---

Well the message to be cancelled is WM_DESTROY, which I found using Winspector Spy. So I went looking for a way to hook the chat window. I found the mentioned thread and started looking into it.
In the included textfile I found a function to discard specific messages, which I believe is what I'm looking for (please tell me if I'm wrong).

problem is, when I try to hook the message window using

code:

---

    Interop.Call(MsgPlus.ScriptFilesPath + "\\dscwpmsg.dll", "SetCWPMSGHook", ChatWnd.Handle, 1, 1)

---

quote:

---

dscwpmsg.txt
Return Value:

2, if both of the Hooks were installed rsp. released successfully,
1, if one of the Hooks was installed rsp. released successfully,
0 (Zero) otherwise.

---

quote:

---

Originally posted by Jesus
Well the message to be cancelled is WM_DESTROY

---

that makes sense indeed, the only problem is that I don't see any WM_CLOSE messages in the window's message list (screenshot)

i know someone that could make this for you probally

jesus, there are many different kind of hooks and methods. And for each specific thing you want to do you need different kinds and different approaches. You can't base your code on some listing which does something completely different (refering to the thread you listed).


What you in the first place need to prevent closing of a window is subclassing. You need to trap WM_CLOSE in the window's windows messages stream.

This means that you will need to redirect the windows messages stream (often called the 'WindowProc') to a function in your program (note: this can not be done in JScript) with a callback function.

In that callback function you simply pass thru all the messages the window will recieve (which are a massive load) to the default WindowProc. Only when WM_CLOSE is detected your callback function must not do anything and thus will effectivly cancel this windows message out.

To subclass a window all you need to do is to change its main window proc address to the address of your callback function so that is called instead. (and in your callback procedure calls the original windowproc procedure of the Window).

An easy (VB6) example explaning all this: http://www.osix.net/modules/article/?id=653



However, you probably also need a system wide or application wide hook to know when a window is opened, so you can get its handle and subclass it. (you could also use a timed loop for this to poll for any newly opened windows, so you don't need a hook at all, but that is rather a more crappy way of doing it imho).

Or if you're writing a DLL to be loaded in a Plus! script, you can of course simply use the Plus! scripting event ChatWndCreated to pass the handle of the chat window to your DLL which on its turn subclass that chat window.

quote:

---

Originally posted by Delphi Thunderbolt
I grabbed this from a Delphi forum, which you could probably use in a DLL and call the function from your script. Take note of the bolded pieces of code.

---

Yeah, sorry there. Just realised it after re-reading the code.

It may be useful to someone, somewhere so Ill leave it.

thanks for the replies, I know a bit of VB programming so I'll try it with the help of the links and info you all provided me.