[GRASS5] New socket code report
Eric G . Miller
egm2 at jps.net
Tue Feb 13 01:46:32 EST 2001
On Tue, Feb 13, 2001 at 11:07:56AM +0700, Justin Hickey wrote:
> Hi Eric
> Congratulations, the socket code compiles and works on SGI's! A few
> observations from a quick trial run.
Good to hear it's working on SGI, now only 10e23 platforms to go... ;)
> The only problems I saw (2 of them) concern interaction with tcltkgrass.
> They are probably related since they deal with stopping the monitors. If
> you choose to stop a monitor in tcltkgrass, or choose the "stop all x
> monitors" option when you quit, it seems that Grass kills the monitors
> (after stopping x0 I can start x0 again), but the actual windows remain
> on the screen. Starting another x0 opens a new window, giving two
> windows labeled x0. Of course, only one of them accepts graphics
> commands. Note that this effect does not happen if I use the d.mon
> command from the Grass shell, only with tcltkgrass. I'm not sure what's
> happening with that one.
Weird. I hardly ever use TclTkGrass, so I haven't even checked. I don't
know what it does to close all the monitors; I assumed it would just
shell out a "d.mon stop=x<n>" for each monitor. I dunno?
> Anyway, thanks again for the great work. I think we should make sockets
> the default process communication mechanism since it eliminates the
> createfifos.sh script.
Well, that would be my position ;) Of course, I'm biased...
Eric G. Miller <egm2 at jps.net>
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'
More information about the grass-dev