On Mon, Feb 20, 2012 at 6:38 AM, Vitaliy Margolen wine-devel@kievinfo.com wrote:
- return CreateEventA(NULL, FALSE, FALSE, "Fake
MemoryResourceNotification");
I don't think you want a named event here. Anonymous would be better, in case the program will ask for another event.
Oh, right. Anonymous it is, then.
Hang on - those events will never fire, so what does it matter if the same event gets two handles?
My bad. Was just trying to make sure it won't conflict with anything.
Re-read description of this function on MSDN which indicates it's a system wide event. So you should be good with the named event.
Good, the patch stands then. - Dan