Re: startup programs priority, notification area and gnomemeeting.
On Wed, Mar 12, 2003 at 10:23:43AM +0100, Miguel Rodríguez wrote:
> El mié, 12 de 03 de 2003 a las 10:18, Sven Luther escribió:
> > On Wed, Mar 12, 2003 at 10:11:11AM +0100, Miguel Rodríguez wrote:
> > > El mié, 12 de 03 de 2003 a las 08:55, Sven Luther escribió:
> > > > On Tue, Mar 11, 2003 at 05:04:59PM +0100, Sven Herzberg wrote:
> > > > > Am Die, 2003-03-11 um 14.23 schrieb Stian Jordet:
> > > > > > So the only problem I have is that screen 2 don't have any window
> > > > > > manager, I have to start it manually... That's the issue I'm looking for
> > > > > > a solution for.
> > > > >
> > > > > Desktop-Preferneces -> Advanced -> Session
> > > > >
> > > > > go into the »Startup-programs« tab and add sawfish with priority 50.
> > > > > this should work.
> > > >
> > > > BTW, i have a problem with gnomemeeting and the gnome notification area.
> > > > Well various problems really.
> > > >
> > > > I launch gnomemeeting minimized in the notification area, but since both
> > > > have the same priority, the gnomemeeting windows flashes quickly at
> > > > startup and at shutdown, which is not nice. I have tried modifying the
> > > > priority of gnomeeting to 55 or the one of the gnome notification area
> > > > to 45, but none of this seem to survive a relaunch of gnome.
> > > >
> > > I have coded support for the notification area in GnomeMeeting, and I'm
> > > sad to inform you that the race you are seeing is in gnomemeeting
> > > itself. Even if the notification area is ready when GnomeMeeting is
> > > launched, it will first show the main window and hide it once it
> > > receives a signal that the icon tray is ready.
> >
> > So, this is a bug in gnomemeeting, can it not be solved ? I am not
> > familiar with the details, but i guess that you would need to search for
> > the notification area before you make the UI visible, or even don't
> > build the UI if you are only going to display in the notification area.
> The problem is that you cannot search for it. We just try to use it, and
> if we get a signal that we succeeded we hide the main window. The
> problem with this signal is that it is asynchronous, as it involves
> several different applications (system-tray, gnomemeeting and window
> manager, i think). We may add a little delay before showing the main
> window, but that would delay the startup.
Well, i think delaying the startup is no problem, since you would choose
this behavior only if you have checked the option to start hidden. So i
think making the default behavior to not show, and if after a delay
(which can be long enough, a few seconds or even 10s of seconds should
be ok), popup a dialog box informing the user about this, ans asking if
the start hidden option should be disabled.
After all, if the user checked the start hidden option, it is because he
don't want to see the option.
Now, what about the problem of the gnomemeeting window appearing at
logout ? This is because the notification area dies before gnomemeeting,
is it not ? Again, i suppose there is code to unhide gnomemeeting if the
notification area dies or something such. A delay can also be used here,
but the correct solution would be to have GM die before the notification
area does, or to have the notification area wait for all its apps to die
before dying itself, or something such.
Friendly,
Sven Luther
Reply to: