EnumWindows (callback: EnumWindowsProc)
InternetConnectW (callback: InternetSetStatusCallback)
EnumDisplayMonitors (callback: MonitorEnumProc)
Here is 3 off the top of my head.
quote:
Originally posted by CookieRevised
Aren't most (if not all) callback functions in the form of:
MessageCode, wParam, lParam ??
Making it actually more like:
code:
// instruct Plus! to make a (callback) function internally and let it return its address
var objCallbacks = {}
objCallbacks['EnumWindows'] = MsgPlus.CreateCallback();
Interop.Call('user32', 'EnumWindows', objCallbacks['EnumWindows'], 0);
function OnFunctionCallback(hCallback, Message, wParam, lParam) {
switch (hCallback) {
Making it almost the same as OnWindowidEvent_MessageNotification???
using this 'convention'/method you would have covered almost all callbacks... (By heart I only know of 1 callback function which uses 1 more parameter; WindowProc)
/me sits beside Matty on his knees begging 
Using the many params was just to make sure all were covered WndProc who cares about we don't need Plus! scripting to subclass Windows thats just too much access to the system.