[GRASS5] closing monitors by click

[Eric G . Miller]

On Tue, Nov 28, 2000 at 04:01:47PM +0000, Markus Neteler wrote:
> Hi all,
> 
> an annoying problem is that you cannot close GRASS monitors
> by mouse click. As being teaching GRASS in seminars, first
> action of students is usually to kill a monitor with a click
> (close of window) which runs the monitor management into troubles.
> 
> Helena told me that in past this procedure of closing was
> *possible* without confusing GRASS. I wish we could (re-)implement
> this.
> 
> Maybe the lock file could be ignored if the x0, x1,.. process
> is killed (by user request).
> 
> But it's really a pain to teach others not to kill a monitor
> but to use d.mon instead (or tcltkgrass).
> 
> Probably someone has an idea for more monitor convenience?
> These monitor troubles are one reason that many people dislike
> GRASS.
> 
> Thanks in advance

After finding that platforms handle the signal() call differently, I'm
convinced this problem is related.  I did a few tests, and the results
seem to indicate the XDRIVER gets blocked somewhere and won't actually
process the destroy event until it gets unblocked.  So, for systems that
are affected, if you click the close button on the monitor, then do
"d.mon -L" (which should work now), the window will immediately close.
This leads me to believe it's blocked on an open() or read() on the _rfd
fifo file descriptor.  I haven't quite tracked it down, but I'm
confident that's part of the problem.

-- 
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'