#9 Access violations due to spurrious WM_USER events

[rakslice]

I'm getting an access violation around every 15 minutes while a script is running. If that wasn't bad enough, after I click OK twxproxy.exe stays running and I have to go kill the process myself.

I'm running Windows 7 Ultimate 64-bit on a Core i7 2600K.

Quick hack to work around it:

The access violation is coming from TWXProxy.dpr:192, where we're trying to dereference the window message's wParam as a TNotificationEvent pointer. I know very little about low level Windows programming, but Goggle found me some suggestions that Delphi might be using a bunch of WM_USER range messages internally (http://www.delphipages.com/forum/showthread.php?t=49257), so under the assumption that it was trying to (mis)interpret one of those, I tried bumping the message type up to WM_USER+105 (the receiving code at TWXProxy.dpr line 189 and the sending code at Core.pas line 227) and the problem went away.

Is this the wrong purpose to be using WM_USER-0x7fff message types for?
"These values cannot be used to define messages that are meaningful throughout an application, because some predefined window classes already define values in this range. For example, predefined control classes such as BUTTON, EDIT, LISTBOX, and COMBOBOX may use these values. "
- http://msdn.microsoft.com/en-us/library/windows/desktop/ms644931\(v=vs.85).aspx

After running into access violations ~ every 15 minutes, I grabbed the v211 source snapshot, and with some wrangling, got it building in Turbo Delphi Lite and then running in the debugger.

Under the assumption that the message might have come from something other than the TWXProxy code, I did a little Googling:

[rakslice]

lol... copy/paste failure. but all the important stuff's there at any rate.