Unless I'm mistaken, you can do single clicks to zoom out with gis.m...I was
doing this today with the zoom out tool.
--
Eric Patton
epatton@nrcan.gc.ca
Since this is agreed, I'd like to rise the case of zooming out tool in
gis.m - could zooming out with a box be abandoned, in favor of zooming out
at each single mouse click?
Who else agrees/disagrees a single click for zoom out is better than
setting the zoom out box?
Maciek
On Wed, 26 Apr 2006 15:03:50 -0300
"Patton, Eric" <epatton@nrcan.gc.ca> wrote:
Unless I'm mistaken, you can do single clicks to zoom out with
gis.m...I was doing this today with the zoom out tool.
True. Haven't checked for quite some time. Last time I used gis.m
setting the window was needed to zoom out I think. Anyway, now single
click works, great!
Talking of gis.m display in general, it is much slower than X11 Grass
display. Especially for vectors, when compared. Could that be easily
improved? Data browsing by panning around and series of zoom in/out are
too slow, for me. gis.m has plenty of great features but I'll rather
still stick to X11 displays for it's more effective. Especially now
that the "100% CPU at mouse bug" is fixed :).
Maciek
--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/
Maciek Sieczka wrote:
Talking of gis.m display in general, it is much slower than X11 Grass
display. Especially for vectors, when compared. Could that be easily
improved?
It depends upon what's causing the slowdown. I don't intend to look
into profiling and optimisation while the task is split across three
separate processes (the d.* client, XDRIVER, and the X server).
The plan is to dispense with drivers altogether; the PNG driver will
be merged with libraster so that d.* modules generate image files
directly. At that point, profiling becomes practical.
If it turns out that software rendering of vectors is inherently slow,
the eventual GUI will need a built-in vector rendering component
(which would need to be implemented separately for each platform).
--
Glynn Clements <glynn@gclements.plus.com>