|
| From: | Andreas Heppel |
| Subject: | Re: Gnustep Applications blocking Adobe Applications on Windows... |
| Date: | Tue, 27 May 2003 16:25:41 +0200 |
I don't know which version of Windows you are running, but this mechanism was at least there until NT 4.0 (the last Windows I work with). And it was not just there, but the common way to implement sockets. NT 4.0 also know the BSD style of programming with sockets, but noone at M$ really told you about that. I have no idea how this is today. But I couls imagine that the BSD API is still there as even the windows events based way to do it, behind the scenes came down to using BSD sockets. It was just a convenient (no flaming, please) encapsulation. So, I can imagine that the BSD style API still exists and could be used. However, I have no idea, why opening a window (which is not so uncommon ;-) can block other apps. And if you say it's particularly Adobe apps, methinks it has something to do with what Adobe is doing.// Create a window which will recieve the socket handling events gnustep_base_wnd = CreateWindow("GNUstepBaseSocketHandler", "", WS_OVERLAPPEDWINDOW, CW_USEDEFAULT, CW_USEDEFAULT, CW_USEDEFAULT, CW_USEDEFAULT, NULL, NULL, hInst, NULL);A native windows window is created here. When this window is omited everything is fine. Adobes applications can now start/stop whenever the want to. The direct circumstances are at present still a bit unclear.So a general question Is this window really needed anymore? Isn't it the case that windows needed a window for socketoperations on Win 3.11 but now is no longer needed.. Can it be removed savely?
Cheers Andreas -- Andreas Heppel Mail: aheppel at web dot de Home: http://www.andreasheppel.de Check out Burn.app - the CD burning frontend for GNUstep http://gsburn.sourceforge.net
| [Prev in Thread] | Current Thread | [Next in Thread] |