[GRASS-dev] Re: GRASS 7 status overview

[Hamish]

Hamish:
> > With continual refresh I worry that ximgview and wximgview will not
> > be much use ssh'ed from the near-dialup connection speeds from home.
> 
> You can use percent=0, in which case it will only update
> when it receives SIGUSR1 (that doesn't work on Windows;
> suggestions?).
> 
> You can use e.g.
> 
>     GRASS_NOTIFY="killall -USR1 `pidof wximgview`"
> 
> to cause SIGUSR1 to be sent whenever a module calls
> D_close_driver().

then I get: 
G7> d.erase 
7682: no process killed

but no refresh.

resizing the window slightly by dragging its window manager frame's
corner a little redraws it.


> OTOH, if the issue is X bandwidth rather than application CPU usage,
> it would be possible to add an option to only perform a redraw if the
> data changes.

wximgview @ percent=100%, top shows:
sshd 20%
wximgview: 11%

the numbers fluctuate a little, but the ratio stays about the same.
(100mbit ssh -X)

> BTW, there is also the wxpyimgview script, which is the same thing but
> written in Python rather than C++. It didn't occur to me to use Python
> until shortly after I'd finished writing wximgview. The original
> reason for using C++ was that I assumed that I would have
> to perform the RGBA->RGB conversion in Python, which would be
> insanely slow; then I realised that I could use NumPy.

@ 100% top shows:
sshd: 16%
python: 15%


...and
ximgview @ 100% top shows:
sshd: 14%
python: 12%


Hamish