discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Gnustep Applications blocking Adobe Applications on Windows...


From: Roland Schwingel
Subject: Re: Gnustep Applications blocking Adobe Applications on Windows...
Date: Wed, 28 May 2003 12:15:24 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

Hi...

aheppel@web.de wrote on 27.05.2003 16:25:41:
> 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).
I tested NT4/2000/XP. All the same problems, for all the same change helped.

> 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 existsand could
> be used.
As far as I am informed - using the window to get sockets running is a relict from Win 3.11. It should work perfeclty without. And as far as I could test yet GNUstep has no problems living without it (I can't test DO, but usual operations are working
as before)

> 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.
Of course Adobe is doing not so nice things here, but IMHO it is also bad
when GNUstep code cannot coexist with applications like Photoshop or Acrobat. And I am sure they will not change their code to adopt to GNUstep. Sun had similar problems with JDK1.2 and they where forced to fix this... But to what I know the window
is redundant at all, so removing will cause no harm and fix this oddity...

Maybe it is the association of the created window to the dll or the "GnustepBaseSocketHandler" windowclass also defined in this file, describing this windows class. After creation there are no messages to this windows (at least gnustep_base_socket_handler() is not called when Photoshop starts).
I tried a lot of things changing this window but nothing helped....

Any further thoughts?

Roland






reply via email to

[Prev in Thread] Current Thread [Next in Thread]