C / C++ / MFC

about "windows belonging to different processes are mixed in a single window hierarchy"

20-Jun-11 11:05

Here's an example project (MFC)[^]

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

xrg_soft@163.com19-Jun-11 17:40

xrg_soft@163.com

19-Jun-11 17:40

From MSDN page for WM_ACTIVATETOPLEVEL
http://msdn.microsoft.com/en-us/library/xkd95027(VS.80).aspx

I got the below description:
This message is similar in use to WM_ACTIVATEAPP, but works in situations where windows belonging to different processes are mixed in a single window hierarchy (common in OLE applications).

Does anybody know where is a example/demo/document available that illustrate "windows belonging to different processes are mixed in a single window hierarchy"?

I googled but found almost nothing.

Thanks!

Re: about "windows belonging to different processes are mixed in a single window hierarchy"

Mark Salsbery19-Jun-11 18:11

Re: about "windows belonging to different processes are mixed in a single window hierarchy"

19-Jun-11 18:11

Since they mention OLE, you could start there perhaps...

Compound Documents[^]

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

xrg_soft@163.com20-Jun-11 19:06

xrg_soft@163.com

20-Jun-11 19:06

Thanks!

I think I got the basic idea.
Just like embeded MS Word into your_app, the embeded MSWord view window is a chid window of your_app.exe but it's essentially relaies on a external process WinWord.exe

so0_lanhlung219-Jun-11 16:56

so0_lanhlung2

19-Jun-11 16:56

i registed my message on DlgMain WM_PK_MESSAGE by RegisterWindowMessage
and i have a DLL..have InjectDLL Function callback to a wndproc
i want my DLL get WM_PK_MESSAGE..
can you have some ideas for me Wink | ;)

tk so much

Re: register window message

xrg_soft@163.com19-Jun-11 17:44

xrg_soft@163.com

19-Jun-11 17:44

Hi,

In each process you using the registered message, you should first call

WM_PK_MESSAGE = RegisterWindowMessage

and then you can use the WM_PK_MESSAGE.

Re: register window message

softwaremonkey19-Jun-11 19:41

softwaremonkey

19-Jun-11 19:41

You also need to use the ON_REGISTERED_MESSAGE macro instead of the normal ON_MESSAGE e.g.

// In message map
BEGIN_MESSAGE_MAP(CMyWnd, CWnd)
  ON_REGISTERED_MESSAGE(m_nRegMsg, OnRegisteredMessage)
END_MESSAGE_MAP()

Moving Objects in small increments

Cyclone_S19-Jun-11 14:07

19-Jun-11 14:07

Hi,

I got a ball hitting a paddle and I want it's X velocity to increase/decrease depending on where it hits the paddle. The code below works with whole numbers but not for numbers like "0.67" or "2.45". I'm looking for a way to animate objects moving at smaller increments for better precision. Thanks.

int speed=Ball_List[b]->speed;
// Paddle center.
int paddle_center = Player->Location.X + Player->Width / 2;

// Ball center.
int ball_center = Ball_List[b]->gameBall->Location.X + Ball_List[b]->gameBall->Width / 2;

// Find the location on the paddle that the ball hit
int paddle_location = ball_center - paddle_center;

// change angle according to distance from center of paddle.
double a=(90-paddle_location);
double angle = (Math::PI / 180) * a; // angle in radians.
Ball_List[b]->xVel = speed*Math::Cos(angle);
Ball_List[b]->yVel = -speed*Math::Sin(angle);

// Move the ball
Ball_List[b]->gameBall->Location = Point(Ball_List[b]->gameBall->Location.X + Ball_List[b]->xVel, Ball_List[b]->gameBall->Location.Y + Ball_List[b]->yVel);
[/code]

enhzflep19-Jun-11 15:03

19-Jun-11 15:03

Can you tell us what doesn't work when you use non-integers. And non-integers for what?

Cyclone_S19-Jun-11 16:03

19-Jun-11 16:03

I tried using doubles but for a value like 0.6 the ball doesn't move at all. The box control takes doubles but will round them down to the nearest integer. Is there a way to do this over the course of X number of frames?

I'm using non-integers for the box control's position. Right now there's only about 6 different directions the ball takes when hitting the paddle. I need finer control over the speed of the ball.

This problem happens with any sort of animation I try to do. What if I wanted smooth acceleration of a game object? This wouldn't be possible with the problem I'm encountering.

enhzflep19-Jun-11 16:23

19-Jun-11 16:23

Ah, okay gotcha.

Well, in that case you can use floats or doubles for the position and the velocity. It's just a matter of rounding the position to an int before using it to display the ball.

Or of course, you could keep an integer position of last impact, along with an integer number of frames since it occured and a double velocity, or position increment per frame. Each time you display, just show the ball at [impact.x + frames*velocity.x, impact.y + frames*velocity.y]

But the easier is to just keep the position and velocity as doubles, converting to an int when using for display purposes. (You might also have to add code that will check if the ball is within a threshold distance, since non-integers will mean your ball wont hit the walls or paddle 'exactly' - well not at the exact moment of a frame, anyway.

Cyclone_S19-Jun-11 16:49

19-Jun-11 16:49

I'm not sure I understand. Do you understand what I'm trying to do? after the ball hits the paddle it should move left/right depending on how far from the center it is. Just need finer precision on the angle(xvel) of the ball. Thanks.

I tried something like this. I took a number like 1.65 and did

1.65 - Math::Floor(1.65)

to get just the decimal part of the number 0.65.Then every frame I added 0.65 to 0.65 and checked if it was >= 1. If it was I added 1.0 to the left/right property of the box. I then repeated that.

The problem with it was I wasn't encounting for the speed of the ball. If the speed of the ball is 6 it moves 6 frames every timer tick. The code I was trying only moved 1 pixel at a time.

I'm just not sure on the math to incorporate the speed into it.

enhzflep19-Jun-11 18:24

19-Jun-11 18:24

Sorry about that. Um, I think I understand your intention.

It sounds to me much like a game of pong or similar. Lord knows what I've done with my old code. I can't be bothered even think about the physics right now, but I've thrown together some code that will throw a red dot into a parabolic arc.

In such a path, we'll have to both be able to have small increments of movement, and be able to vary them. You just have to assign the ball's velocity and position in an appropriate way for your application.

Enjoy. Smile | :)

#include <windows.h>

/*  Declare Windows procedure  */
LRESULT CALLBACK WindowProcedure (HWND, UINT, WPARAM, LPARAM);

/*  Make the class name into a global variable  */
char szClassName[ ] = "CodeBlocksWindowsApp";

int WINAPI WinMain (HINSTANCE hThisInstance,
                     HINSTANCE hPrevInstance,
                     LPSTR lpszArgument,
                     int nCmdShow)
{
    HWND hwnd;               /* This is the handle for our window */
    MSG messages;            /* Here messages to the application are saved */
    WNDCLASSEX wincl;        /* Data structure for the windowclass */

    /* The Window structure */
    wincl.hInstance = hThisInstance;
    wincl.lpszClassName = szClassName;
    wincl.lpfnWndProc = WindowProcedure;      /* This function is called by windows */
    wincl.style = CS_DBLCLKS;                 /* Catch double-clicks */
    wincl.cbSize = sizeof (WNDCLASSEX);

    /* Use default icon and mouse-pointer */
    wincl.hIcon = LoadIcon (NULL, IDI_APPLICATION);
    wincl.hIconSm = LoadIcon (NULL, IDI_APPLICATION);
    wincl.hCursor = LoadCursor (NULL, IDC_ARROW);
    wincl.lpszMenuName = NULL;                 /* No menu */
    wincl.cbClsExtra = 0;                      /* No extra bytes after the window class */
    wincl.cbWndExtra = 0;                      /* structure or the window instance */
    /* Use Windows's default colour as the background of the window */
    wincl.hbrBackground = (HBRUSH) COLOR_BACKGROUND;

    /* Register the window class, and if it fails quit the program */
    if (!RegisterClassEx (&wincl))
        return 0;

    /* The class is registered, let's create the program*/
    hwnd = CreateWindowEx (
           0,                   /* Extended possibilites for variation */
           szClassName,         /* Classname */
           "Click to release a ball",       /* Title Text */
           WS_OVERLAPPEDWINDOW, /* default window */
           CW_USEDEFAULT,       /* Windows decides the position */
           CW_USEDEFAULT,       /* where the window ends up on the screen */
           544,                 /* The programs width */
           375,                 /* and height in pixels */
           HWND_DESKTOP,        /* The window is a child-window to desktop */
           NULL,                /* No menu */
           hThisInstance,       /* Program Instance handler */
           NULL                 /* No Window Creation data */
           );

    /* Make the window visible on the screen */
    ShowWindow (hwnd, nCmdShow);

    /* Run the message loop. It will run until GetMessage() returns 0 */
    while (GetMessage (&messages, NULL, 0, 0))
    {
        /* Translate virtual-key messages into character messages */
        TranslateMessage(&messages);
        /* Send message to WindowProcedure */
        DispatchMessage(&messages);
    }

    /* The program return-value is 0 - The value that PostQuitMessage() gave */
    return messages.wParam;
}

////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////
float ballPosX, ballPosY, ballVelocityX, ballVelocityY;
const int myTimerId = 1;
const int intervalMs = 50;

VOID CALLBACK myTimerProc(HWND hwnd,        // handle to window for timer messages
    UINT message,     // WM_TIMER message
    UINT idTimer,     // timer identifier
    DWORD dwTime)     // current system time
{
	ballPosX += ballVelocityX;
	ballPosY += ballVelocityY;
	ballVelocityY -= 0.1;
	InvalidateRect(hwnd, NULL, true);
}

/*  This function is called by the Windows function DispatchMessage()  */
LRESULT CALLBACK WindowProcedure (HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam)
{
	PAINTSTRUCT ps;
	HDC hdc;

    switch (message)                  /* handle the messages */
    {
        case WM_DESTROY:
            KillTimer(hwnd, myTimerId);
            PostQuitMessage (0);       /* send a WM_QUIT to the message queue */
            break;

        case WM_PAINT:
            hdc = BeginPaint(hwnd, &ps);

            SetPixel(hdc, ballPosX, ballPosY, RGB(250,0,0));
            SetPixel(hdc, ballPosX, ballPosY+1, RGB(250,0,0));
            SetPixel(hdc, ballPosX+1, ballPosY, RGB(250,0,0));
            SetPixel(hdc, ballPosX+1, ballPosY+1, RGB(250,0,0));

            EndPaint(hwnd, &ps);
            break;

        case WM_LBUTTONUP:
            ballPosX=0;
            ballPosY=0;
            ballVelocityX=3.2;
            ballVelocityY=8.1;

            KillTimer(hwnd, myTimerId);
            SetTimer(hwnd, myTimerId, intervalMs, myTimerProc);
            break;

        default:                      /* for messages that we don't deal with */
            return DefWindowProc (hwnd, message, wParam, lParam);
    }

    return 0;
}

enhzflep19-Jun-11 21:35

19-Jun-11 21:35

I got bored. Here try if this if you like - it's two balls, a red one and a white one. If you hit the red one with the white one it will move in a direction away from the white one before being slowed to a halt by friction. Of course your collision handling stuff will be different(hopefully pixel-accurate, unlike mine) for the paddle and the ball, but it's the same concepts at work.

Rose | [Rose]

#include <math.h>
#include <windows.h>
#include <windowsx.h>
#include <wingdi.h>

/*  Declare Windows procedure  */
LRESULT CALLBACK WindowProcedure (HWND, UINT, WPARAM, LPARAM);

void handleCollisions();

/*  Make the class name into a global variable  */
char szClassName[ ] = "CodeBlocksWindowsApp";

int WINAPI WinMain (HINSTANCE hThisInstance,
                     HINSTANCE hPrevInstance,
                     LPSTR lpszArgument,
                     int nCmdShow)
{
    HWND hwnd;               /* This is the handle for our window */
    MSG messages;            /* Here messages to the application are saved */
    WNDCLASSEX wincl;        /* Data structure for the windowclass */

    /* The Window structure */
    wincl.hInstance = hThisInstance;
    wincl.lpszClassName = szClassName;
    wincl.lpfnWndProc = WindowProcedure;      /* This function is called by windows */
    wincl.style = CS_DBLCLKS;                 /* Catch double-clicks */
    wincl.cbSize = sizeof (WNDCLASSEX);

    /* Use default icon and mouse-pointer */
    wincl.hIcon = LoadIcon (NULL, IDI_APPLICATION);
    wincl.hIconSm = LoadIcon (NULL, IDI_APPLICATION);
    wincl.hCursor =LoadCursor (NULL, IDC_ARROW);
    wincl.lpszMenuName = NULL;                 /* No menu */
    wincl.cbClsExtra = 0;                      /* No extra bytes after the window class */
    wincl.cbWndExtra = 0;                      /* structure or the window instance */
    /* Use Windows's default colour as the background of the window */
    wincl.hbrBackground = (HBRUSH) COLOR_BACKGROUND;

    /* Register the window class, and if it fails quit the program */
    if (!RegisterClassEx (&wincl))
        return 0;

    /* The class is registered, let's create the program*/
    hwnd = CreateWindowEx (
           0,                   /* Extended possibilites for variation */
           szClassName,         /* Classname */
           "Click to release a ball",       /* Title Text */
           WS_OVERLAPPEDWINDOW, /* default window */
           CW_USEDEFAULT,       /* Windows decides the position */
           CW_USEDEFAULT,       /* where the window ends up on the screen */
           544,                 /* The programs width */
           375,                 /* and height in pixels */
           HWND_DESKTOP,        /* The window is a child-window to desktop */
           NULL,                /* No menu */
           hThisInstance,       /* Program Instance handler */
           NULL                 /* No Window Creation data */
           );

    /* Make the window visible on the screen */
    ShowWindow (hwnd, nCmdShow);

    /* Run the message loop. It will run until GetMessage() returns 0 */
    while (GetMessage (&messages, NULL, 0, 0))
    {
        /* Translate virtual-key messages into character messages */
        TranslateMessage(&messages);
        /* Send message to WindowProcedure */
        DispatchMessage(&messages);
    }

    /* The program return-value is 0 - The value that PostQuitMessage() gave */
    return messages.wParam;
}

////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////
float ballPosX, ballPosY, ballVelocityX, ballVelocityY;
float curMouseX, lastMouseX, curMouseY, lastMouseY;
int clientWidth, clientHeight;

const int myTimerId = 1;
const int intervalMs = 50;
const int ballRadius = 10; // pixels
const int cursorRadius = 15; // pixels


void handleCollisions()
{
    float dx, dy, dist;

    // part 1 - check for collisions with the mouse cursor
    dx = ballPosX - curMouseX;
    dy = ballPosY - curMouseY;

    dist = sqrt( dx*dx + dy*dy);
    if (dist<ballRadius+cursorRadius)
    {
        ballVelocityX = 0.5 * dx;
        ballVelocityY = 0.5 * dy;
    }

    // part 2 - check for collisions with the walls
    if (ballPosX < ballRadius)
        ballVelocityX = abs(ballVelocityX);

    if (ballPosY < ballRadius)
        ballVelocityY = abs(ballVelocityY);

    if (ballPosX > clientWidth-ballRadius)
        ballVelocityX = -1 * abs(ballVelocityX);

    if (ballPosY > clientHeight-ballRadius)
        ballVelocityY = -1 * abs(ballVelocityY);
}

VOID CALLBACK myTimerProc(HWND hwnd,        // handle to window for timer messages
    UINT message,     // WM_TIMER message
    UINT idTimer,     // timer identifier
    DWORD dwTime)     // current system time
{
	ballPosX += ballVelocityX;
	ballPosY += ballVelocityY;
	ballVelocityX *= 0.9;
	ballVelocityY *= 0.9;

    handleCollisions();

	InvalidateRect(hwnd, NULL, true);
}

/*  This function is called by the Windows function DispatchMessage()  */
LRESULT CALLBACK WindowProcedure (HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam)
{
	PAINTSTRUCT ps;
	HDC hdc;
    RECT clientRect;

    HBRUSH newBr, oldBr;


    switch (message)                  /* handle the messages */
    {
        case WM_CREATE:
            ballPosX = 100;
            ballPosY = 100;
            SetTimer(hwnd, myTimerId, intervalMs, myTimerProc);
            GetClientRect(hwnd, &clientRect);
            clientWidth = clientRect.right;
            clientHeight = clientRect.bottom;
            return true;

        case WM_DESTROY:
            KillTimer(hwnd, myTimerId);
            PostQuitMessage (0);       /* send a WM_QUIT to the message queue */
            break;

        case WM_PAINT:
            hdc = BeginPaint(hwnd, &ps);

            //draw the red ball
            newBr = CreateSolidBrush(RGB(250,0,0));
            oldBr = (HBRUSH)SelectObject(hdc, newBr);
            Ellipse(hdc, ballPosX-ballRadius,ballPosY-ballRadius,ballPosX+ballRadius,ballPosY+ballRadius);
            SelectObject(hdc, oldBr);
            DeleteObject(newBr);

            // draw the white ball
            Ellipse(hdc, curMouseX-cursorRadius, curMouseY-cursorRadius, curMouseX+cursorRadius, curMouseY+cursorRadius);

            EndPaint(hwnd, &ps);
            break;

        case WM_MOUSEMOVE:
            lastMouseX = curMouseX;
            lastMouseY = curMouseY;
            curMouseX = GET_X_LPARAM(lParam);
            curMouseY = GET_Y_LPARAM(lParam);
            InvalidateRect(hwnd,NULL,true);
            break;

        case WM_LBUTTONUP:
            // shoot the red ball from the top left corner
            ballPosX=11;
            ballPosY=11;
            ballVelocityX=6.2;
            ballVelocityY=18.1;
            break;

        default:                      /* for messages that we don't deal with */
            return DefWindowProc (hwnd, message, wParam, lParam);
    }

    return 0;
}
}

Cyclone_S20-Jun-11 14:33

20-Jun-11 14:33

Thanks for the examples. The first one has smooth transitions in motion. Exactly what I need. However I'm using .net(managed code) not winAPI. It seems .net rounds the floats down to a whole number?

Would you be able to help me with the formula for moving an object using my previous post idea?

Thanks.

enhzflep20-Jun-11 18:45

20-Jun-11 18:45

That's okay. I had fun playing around with it.

Cyclone_S wrote:
However I'm using .net(managed code) not winAPI. It seems .net rounds the floats down to a whole number?

I'd be very surprised.
You're not giving it the impression that this is your intention, by (I don't know, say) multiplying floats with ints - I've no idea what the result is - real or integer..

I don't understand, you have the formula for moving the ball. - BallPos += Velocity - You also have a way of applying gravity or friction - just alter the velocity.

Perhaps you'd be better off in the right forum?
Perhaps
http://www.codeproject.com/Forums/3785/Managed-Cplusplus-CLI.aspx[^]
or
http://www.codeproject.com/Forums/1649/Csharp.aspx[^]

All the best. Smile | :)

WSA Events

csrss19-Jun-11 3:32

19-Jun-11 3:32

Hi. I got the following situation,

void FunctionA(some params)
{
// do something
SOCKET sock = create new socket();
WSAEVENT hEvent = new event();
wsaeventselect(sock, event, some flags);
FunctionB(sock);
delete event();
}

void FunctionB(sock)
{
// here do something else with a socket
}

The thing is, i dont have access to FunctionA() but it calls

FunctionB()

, where i am the master and can do anything. In function B i am receiving a socket which has an event associated with it but nothing else. I got no handle to an event - nothing, just a socket. Is there any way to get this event handle having only socket descriptor? If there is no such API, windows system should store these events somewhere, right? Is there any way to dig into this place and grab events from there?
Thanks

011011010110000101100011011010000110100101101110
0110010101110011

enhzflep19-Jun-11 4:13

19-Jun-11 4:13

I don't know anything at all about WSA sockets, save for the few crumbs I just picked up reading the winsock function reference at msdn.

However, I can see nothing to indicate this to be the case - nor can I think of a reason why this would necessarily be included - i.e if it's a socket you've created, then surely it is also you thas already attached said event to it - in which case you'd already have it's handle.. At least that's the way I guess it.

With that in mind, and the preparedness to go poking about in windows' memory space, I'd suggest that there is likely to be a far simpler way - unless of course FunctionA is in the kernel.
When FunctionB ends, it has to be able to return control to FunctionA, right? With this address available, you can look at the (machine) code for FunctionA, so with a little fancy footwork you can easily get the location in memory of the variable that is used to store the newly created event, and snatch the handle from there..

You know how I'd go about it? I'd write a dummy FunctionB, and put a statement something like

printf("here is my marker");

I'd then fire-up the program in OllyDbg, and search for refferences to "here is my marker". When I'd found the place that the memory containing this string was referenced, I'd know that I'd found my FunctionB. From there I would simply place a break-point inside my function, start the program running and wait for it to hit the break-point. Single-stepping would then allow me to return to FunctionA, where I could grab the required handle from the memory it was originally stored into.

Might take 30 mins to come up with working code for a real FunctionB to grab the event handle, so long as there's no bumps along the way like protected memory. I forget how to go about reading a process's memory but I've got code some where to do it.

You sure have got me curious about your project.. Thumbs Up | :thumbsup:

csrss19-Jun-11 5:43

19-Jun-11 5:43

The thing is, socket is not created by me. Well, i was able to grab a list of events using ntquerysysteminformation and ntqueryobject but there seems to be no way to find out if a current event was selected by WSAEventSelect for a specified socket. enhzflep, this rather must be "out-of-the-box-working-template-automated-appliable-to-everything" code :P
Seems like the easiest way would be to just insert inline hook, but more hooks - less stable the app become =/

011011010110000101100011011010000110100101101110
0110010101110011

Mark Salsbery19-Jun-11 9:38

19-Jun-11 9:38

Even if you could get the event handle, what would you do with it? I assume you also don't have control over how the event is being used so you won't have any synchronization with whatever thread(s) are already using the event...

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

csrss19-Jun-11 13:13

19-Jun-11 13:13

There are lots of things i can do with event, Mark. I can wait on it, so i dont have to deselect old event and select new one, so the original thread have a control over this original event. I can block signaling this event and signal it when i am done with my job, so original thread will be notified when it is appropriate.

011011010110000101100011011010000110100101101110
0110010101110011

Mark Salsbery19-Jun-11 14:10

19-Jun-11 14:10

csrss wrote:
I can wait on it, so i dont have to deselect old event and select new one, so the original thread have a control over this original event

Then do you have a race condition? Which thread calls WSAEnumNetworkEvents() first? Or is only one FD_XXX event being "listened for" so WSAEnumNetworkEvents() isn't called?

csrss wrote:
I can block signaling this event and signal it when i am done with my job

How do you block signalling of an event (just curious...I didn't know it was possible since I've never needed to)?

You must have intimate knowledge of the existing code to believe this is feasible Smile | :)

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

csrss20-Jun-11 5:46

20-Jun-11 5:46

This is actually more an experiment then a real life solution - i am trying to create my own layer without writing and installing one. It looks like this: some event is created in some function which sends some data over a socket:

WSAEVENT hEvent = WSACreateEvent();
::WSAEventSelect(sock, hEvent, FD_WRITE | FD_READ);
WSASend(....);

And then a thread waits for event, in fact event occurs when we got some bytes waiting for us or when we are able to write some bytes. WSASend is out of the question here, because all my job is done before WSASend gets executed. The pain is WSARecv, because after this call i have some thing to do and after i am done i can return control to a function which waits for WSARecv to complete. BTW, i am hooking these calls so when WSAsomething is called control goes to my function, where i am calling WSAsomething and additionally do some work with outgoing || incoming data.
So the thing is to prevent WSAsomething completion event signaling and signal it when i am done with my part.

I know it is wrong :P and all bad things might happen and there can be a disaster crash or something and this is not what i am going to implement in final solution. I am trying and learning how to dig into system and control it in every ways possible. About blocking event, well, i can save old event handle, select new event, do my stuff, and when done, - signal old event and delete mine, for example :P Or i can go deeper into the cave and try to hook something here and there and do some crazy stuff, you know Big Grin | :-D

011011010110000101100011011010000110100101101110
0110010101110011

Mark Salsbery20-Jun-11 9:29

20-Jun-11 9:29

csrss wrote:
About blocking event, well, i can save old event handle, select new event, do my stuff, and when done, - signal old event and delete mine,

Right. Problem is, when the event is signaled, WSAEnumNetworkEvents() is usually called by the waiting/polling thread to determine which event(s) occurred. Only one thread can make that call for a given event signal on a given socket (even if you duplicate the socket) because the call resets its event status.

Good luck though Smile | :)

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

csrss20-Jun-11 10:17