I have now only come to realize the issue with WM_PAINT message being captured. If you register the WM_PAINT message and don't return it to the window, it actually will prevent WLM from repainting as well.
To test this theory import the script, open a conversation window, click the Enable button on the Scripts window then try typing you will notice no characters appear until you click the Disable button.
How come patchy does the script capture WM_PAINT from other windows aside from its own? Is this an issue with the script engine and that specific message?
I realize this is in the Scripting Docs
quote:
Originally posted by Scripting Docs
Remarks
In case of doubt, always return -1 to make sure the message is properly received and interpreted by the window. Preventing standard system messages (like WM_PAINT) to be processed by the window can have disastrous effects.
However none of the other Messages are processed on a Process Wide basis (it seems).
/ 
Attachment: 
