[772] in Athena User Interface
Re: xalf and netscape
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu May 17 10:22:38 2001
Message-Id: <200105171422.KAA10233@egyptian-gods.MIT.EDU>
To: Abby Fox <ajfox@MIT.EDU>
cc: aui@MIT.EDU
In-Reply-To: Your message of "Thu, 17 May 2001 09:58:22 EDT."
<200105171358.JAA13478@whirlwind.mit.edu>
Date: Thu, 17 May 2001 10:22:35 -0400
From: Greg Hudson <ghudson@MIT.EDU>
> With netscape already open, if I select a menu item which launches a
> web page (either using htmlview or beland's original
> gnome-moz-remote command), it launches fine but the hourglass stays
> up for about a minute and a half, which I'm guessing may be the
> generic timeout.
> Any bright ideas here, or am I missing something?
Well, we have two options to make the right thing happen:
1. We can turn off the GNOME xalf integration (a one-line
change) and go back to explicitly running xalf in launchers
and menu items which we expect to be slow launching.
2. We could make xalf turn off the display hack when its child
process exits. xalf already has code to do this, but it is
commented out because:
/* Most of the code in this function is disabled, because if one have
shellscripts that starts the application in the background, the script
will immediatley exit. Nevertheless, we should keep tracking the launch. */
I don't think we make a habit of using shell scripts which start
applications in the background, so we could probably turn this code
back on.
