🎉 Celebrating 25 Years of GameDev.net! 🎉
Not many can claim 25 years on the Internet! Join us in celebrating this milestone. Learn more about our history, and thank you for being a part of our community!
Async Windows Message
Author
Yo. I''m having trouble defining my Windows message when i declare my socket as an Async socket. I get the impression you can call it whatever you want right? Like WM_ASYNC or WM_WSAASYNC or whetever. However, I get an error saying my message declaration (in the function) is an undefined constant and in the callback function case statement I get an error saying the case expression is not constant. What''s goin on here??
==============================
"Need more eeenput..."
- #5, "Short Circuit"
==============================
You need to assign a numerical value to your windows message.
So if you use WM_ASYNC you should have somewhere:
#define WM_ASYNC (WM_USER + 5)
(or some other value instead of 5) or use a const statement.
const int WM_ASYNC = WM_USER + 2;
So if you use WM_ASYNC you should have somewhere:
#define WM_ASYNC (WM_USER + 5)
(or some other value instead of 5) or use a const statement.
const int WM_ASYNC = WM_USER + 2;
I thought the socket sent your winproc those msg''s when it recieved a packet (ie you shouldn''t be sending them)
Just talking out my arse though...
Just talking out my arse though...
Magmai Kai Holmlor: The third argument to the WSAAsyncSelect() call is the window message that will posted by winsock when an network event occurs. You need to know it''s numerical value both for the call to WSAAsyncSelect() and in order to register your message handler within the message pump.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
