Hello,
I sometimes connect from home to my work computer via ssh and launch 5.1
through this connection with X forwarding. Everything works quite well,
except for d.what.vect which is extremely slow in starting up and in
giving back the cross cursor after displaying information about an object.
Any ideas why this would be ?
Moritz
On Mon, 2 Jun 2003, Moritz Lennert wrote:
Hello,
I sometimes connect from home to my work computer via ssh and launch 5.1
through this connection with X forwarding. Everything works quite well,
except for d.what.vect which is extremely slow in starting up and in
giving back the cross cursor after displaying information about an object.Any ideas why this would be ?
This is probably similar to the problem with d.what.sites, since the
'flashing sites' feature was added. Glynn gave some reasons why it might
be very slow over a slow network connection here:
http://www.intevation.de/rt/webrt?serial_num=1759&display=History
I have also noticed from my extremely limited testing of 5.1 that
d.what.vect is very slow just on a slow computer even when working
directly at the console. Maybe the 'flashing' feature needs tidied up a
bit.
Paul
Moritz Lennert wrote:
I sometimes connect from home to my work computer via ssh and launch 5.1
through this connection with X forwarding. Everything works quite well,
except for d.what.vect which is extremely slow in starting up and in
giving back the cross cursor after displaying information about an object.Any ideas why this would be ?
Because someone decided to add a gimmick (flashing the selected line)
to d.what.vect without thinking about how it would impact the X
bandwidth.
The code involves saving and restoring the entire window contents via
a file, which means transferring the data over the X connection (in
both directions, multiple times).
Note: I didn't merge these changes into the release branch for this
reason. I suggest that you simply use an older version.
--
Glynn Clements <glynn.clements@virgin.net>
On Tuesday 03 June 2003 10:25, Paul Kelly wrote:
On Mon, 2 Jun 2003, Moritz Lennert wrote:
> Hello,
>
> I sometimes connect from home to my work computer via ssh and launch 5.1
> through this connection with X forwarding. Everything works quite well,
> except for d.what.vect which is extremely slow in starting up and in
> giving back the cross cursor after displaying information about an object.
>
> Any ideas why this would be ?This is probably similar to the problem with d.what.sites, since the
'flashing sites' feature was added. Glynn gave some reasons why it might
be very slow over a slow network connection here:
http://www.intevation.de/rt/webrt?serial_num=1759&display=HistoryI have also noticed from my extremely limited testing of 5.1 that
d.what.vect is very slow just on a slow computer even when working
directly at the console. Maybe the 'flashing' feature needs tidied up a
bit.
I think, that this is caused by my hack for R_get_location_with_*(),
which makes possible to quit this function from module. It is done so,
that the xdriver is sending info 'nothing happened' to the module and
the module respondes 'go on'. This works in loop and consumes
processor time and everything becomes slow.
Radim
Radim Blazek wrote:
> > I sometimes connect from home to my work computer via ssh and launch 5.1
> > through this connection with X forwarding. Everything works quite well,
> > except for d.what.vect which is extremely slow in starting up and in
> > giving back the cross cursor after displaying information about an object.
> >
> > Any ideas why this would be ?
>
> This is probably similar to the problem with d.what.sites, since the
> 'flashing sites' feature was added. Glynn gave some reasons why it might
> be very slow over a slow network connection here:
> http://www.intevation.de/rt/webrt?serial_num=1759&display=History
>
> I have also noticed from my extremely limited testing of 5.1 that
> d.what.vect is very slow just on a slow computer even when working
> directly at the console. Maybe the 'flashing' feature needs tidied up a
> bit.I think, that this is caused by my hack for R_get_location_with_*(),
which makes possible to quit this function from module.
No, that isn't the problem. Both d.what.vect and d.what.sites were
modified to "flash" the selected line/site. This works by saving the
screen contents with R_panel_save(), then repeatedly drawing the
"flash" then erasing it with R_panel_restore(). Each call to the
R_panel_* functions sends the entire screen contents over the X
connection (XGetImage(), XPutImage()), which is what makes it so slow.
--
Glynn Clements <glynn.clements@virgin.net>