[winGRASS] d.mon socket problem

[John Huddleston]

To WinGrass list,

The problem is not with Grass5; rather with the Cygwin XWin.

Yes, with the Cygwin XWin you do have to select=x0 to make
it work.  Plus, there seems to be some generic timeout on
the Cygwin XWin. Not sure what it is but I will continue to
track it.

If I use my X-Win32 version 5.0.1 build 1 then Grass5 d.mon x0
starts up with a black screen and it works as advertised.

John Huddleston

-----Original Message-----
From: wingrass-admin at grass.itc.it [mailto:wingrass-admin at grass.itc.it]On
Behalf Of Glynn Clements
Sent: Tuesday, May 20, 2003 9:55 AM
To: Markus Neteler
Cc: wingrass at grass.itc.it
Subject: Re: [winGRASS] d.mon socket problem



Markus Neteler wrote:

> A winGRASS problem still present is:
> 
> GRASS >d.mon x0
> Socket is already in use or not accepting connections.
> Use d.mon to select a monitor
> Problem selecting x0. Will try once more
> 
> -> the monitor window opens, but is not yet accessible.
>    The socket file in /tmp/grass-$USER/ is generated
> 
>    The background is grey
> 
> GRASS: > d.mon select=x0
> 
> -> now the monitor works (d.rast etc)
>    The socket file is not touched a second time.
>    The background is black as expected.

1. Is this with the "generic" version or the X11 version?

2. Are you saying that display commands don't work until you have
performed an explicit "d.mon select..."?

-- 
Glynn Clements <glynn.clements at virgin.net>
_______________________________________________
winGRASS mailing list
winGRASS at grass.itc.it
http://grass.itc.it/mailman/listinfo/wingrass