quote:
Originally posted by effection
very very nice piece of work
Thanks.
quote:
Originally posted by CookieRevised
No need for an ActiveX for all of this. Just some API stuff... In fact, the ActiveXs do exactly what you already can do in Plus! by using the Windows API.
Though using this ActiveX might be the easy solution for some. So, very good and nice find though 
...
Would you be able to give an example of such a code (using only Plus! and the Windows API)? I'm quite interested in knowing how to do this. I didn't think it would be possible to have real-time events (when the windows messages are received), even with the new Interop.GetCallbackPtr() which only supports synchronous calls (I assume this means the calls are returned immediately).
quote:
Originally posted by CookieRevised
I actually do not recommend all of this (even including the use of <OleFiles>). (I think Patchou will shoot me now 
) The reason is again that you will get into trouble when more than one script is going to use that DLL and you later install or remove even more scripts which use it.
I just experimented with this and noticed that it does cause a few problems. However, the ActiveX is not completely unregistered and the script's functionality returns to normal after restarting WLM.
quote:
Originally posted by CookieRevised
As for the tabbed chat window example, I think that can be done much easier and with subclassing just 1 window. The hidden Plus! window which controls the tabs.
Hmm... I tried subclassing just the hidden Plus! window, but I wasn't sure which message needed to be detected (WM_ACTIVATE doesn't work with it). The problem is that tabs can be changed with left mouse clicks as well as ctrl+tab on the keyboard. Also, subclassing each individual conversation window makes it easier to keep track of the current conversation handle. Suggestions?
I've also updated the TabbedStatusIcon to fix a few bugs.
/ 
