Thanks for answering my earlier post about socket trouble. The trouble is my server stopped listening for new connections (Connrefused error when client connects) but old connections are alive & still receiving handshakes.
Clients couldn't get connected even hr's after. I've found the reason, my server works fine if connections arrives one by one, but when simultaneous connections arrive, the events(WSAWaitForMultipleEvents) which i used in loop stops triggering. Without events the server works fine (accepts simultaneous connections).
I'm posting crtical section of my code, could some one give me a possible solutions...
A.exe use createprocess to start up B.exe,
B.exe must read a local file in its folder,
i found i only click B.exe, B.exe can open the local file,
when A.exe start up B.exe using createprocess,
B.exe fails to open the local file always.
when i put these code in a console program, the sub process can open correctly. Then in my windows program, the sub process can't open file firstly, then start up the sub process again (my program will start up the sub process every 20 sec) , it's OK.
hi all ,
i am facing a problem while displaying 2 byte japanese characters in web page.
actually what i m doing is reading the japanese string as a string and then writting it to xml file and then use the xml file to fill the web page .
so what i m getting is single byte characters corresponding to the the japanese chracters.
If anyone has any answer then please reply
Anyone know the reason why the WS_MAXIMIZE style bit isn't taking effect when I don't also specify the WS_POPUP for the window's style? MSDN doesn't suggest it's ignored, although a quick Google leads me to believe it could be for overlapped windows.
I need to initially maximize a window during the app startup. I've always used ShowWindow() in the past when maximizing a window without much headache, but now I need to control the order in which this happens moreso to avoid unsightly drawing issues as I need to perform quite a few tasks during the startup (working on my first 3D game). As such, I'd rather have it maximized before the window is shown rather than after and don't want to go through the trouble of screwing around with the message queue to deal with it.
Surely there must be a simple way for an overlapped window?
How is ShowWindow() called? In most applications, ShowWindow() is called *after* you've called CreateWindow(), hence making your window seemingly ignore your flags. In MFC apps, what's passed to the mainwindow's ShowWindow(), is whatever the process has been fed (settings on shortcut, spawning process, etc).
Jeremy Falcon wrote:
As such, I'd rather have it maximized before the window is shown rather than after and don't want to go through the trouble of screwing around with the message queue to deal with it.
You don't need to fiddle with WS_MAXIMIZE. Just create the window without the WS_VISIBLE flag. Then call ShowWindow() with SW_SHOWMAXIMIZED. No screwing around with the message queue.
100% natural. No superstitious additives.
Last Visit: 31-Dec-99 18:00 Last Update: 24-Sep-21 18:41