quote:
Originally posted by Doublevil
and return "/psm /psm [your message here]"
Doesn't that mean there is also a command parsing bug in Plus!?....
This said, your use of the
OnEvent_ChatWndSendMessage to work around the PSM limitaton is interesting, but can't you just use
oChatWnd.SendMessage("/psm blahblah") or
oChatWnd.SendMessage("/psm /psm blahblah") in that case?
(Can't test because I don't run WLM 2011 atm)
quote:
Originally posted by Doublevil
I don't know how to close it, though.
What most people do:
Interop.Call("User32", "SendMessageW", oChatWnd.Handle, 0x10 /*WM_CLOSE*/, 0,0);
Or in a more gracefull/safer way:
Interop.Call("User32", "PostMessageW", oChatWnd.Handle, 0x0111 /*WM_COMMAND*/, 0x9C51, 0);
Or with the use of Plus! scripting functions:
oChatWnd.SendMessage("/close")
---
However, note that using the
SendMessage function might not always work. You always need to check if the typing box is actually enabled and if it can recieve commands (using
oChatWnd.EditChangeAllowed)
PS: instead of using a chatwindow, you might also wanna try sending the string to the word wheel edit box (the
search box) in the contact list. However, that can't be done directly with pure scripting though. You probably need some Windows API for that or worse Active Accessebility.
/ 
