[Top][All Lists]

[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, 4 Jun 2003 08:52:35 +0200

Hello Adam...

After my posting I had a small discussion with Richard about it via mail
and I said I will investigate this further here on my own
for 2 weeks and then call back to him and the list. It still works without
problems here. I just removed the window. And IMHO it should work well
without this window...

I will notify you in about a week...


Adam Fedor <address@hidden> wrote on 03.06.2003 19:44:45:

> On Wednesday, May 28, 2003, at 04:15 AM, Roland Schwingel wrote:
> > > 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?
> >
> >
> I haven't been able to do anything about this. But since you probably
> use GNUstep on Windows as much as or more than anyone, I don't see a
> problem with taking this out and trying to find another way to handle
> sockets (if necessary) later on.

reply via email to

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