Re: Performance on the Linux platform

[Owen Taylor <otaylor redhat com>]

Jason Stokes <jstok bluedog apana org au> writes:

> Owen Taylor wrote:
> > 
> > Jason Stokes <jstok bluedog apana org au> writes:
> > >
> > > Ok, if that's the case why is it possible to start a new instance of gmc
> > > via the footprint menu?  The user isn't going to be care about the
> > > different ways a new window can be created.  If you choose "Close
> > > Window" from the file menu, and the gmc process was only managing one
> > > window, it still runs but you've now lost any way to interact with it,
> > > and have to kill it with a signal, assuming the user understands such
> > > things.  This is not the ideal way for a GUI program to work.
> > 
> > When you use the foot menu, it doesn't create a new process -
> > what happens is that when it launches GMC, GMC checks to see
> > if there is a process already running, and if there is, tells
> > that process to create a new window and exits.
> > 
> > (This still takes longer than just creating a window from
> > a menu, accounting for the original observation)
> > 
> > There should never be a case where more than once GMC is
> > running at a time.
> 
> I can personally vouch for the fact that when I select "File Manager"
> from the foot menu, it starts a new gmc process.  This may be an
> installation problem, since my gnome is built from CVS sources, but it's
> definitely the way it works.

I can't speak for your setup. But I helped Federico write the code to
handle popping up another window when gmc is invoked again, so I can
say that it is suppposed to have only a single process for all windows, 
and has worked properly on many occasions on the past.

Regards,
                                        Owen