In addition to my last email on the subject, here are a few
more oddities I noticed working with gis.m:
1. Module GUI started from gis.m pop up way to narrow. When started
from the console, the default size is fine
2. Changes done to a vector layer using v.digit do not show in
the Map Window, until one switches the Draw Mode
--
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeo-Information Science)
Institut für Ur- und Frühgeschichte
(Institute of Archaeology)
Christian-Albrechts-Universität zu Kiel
Johanna-Mestorf-Straße 2-6
D 24098 Kiel
Germany
Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg
If you click the zoom to current and redraw all, it will show up. I am
changing/renaming this button to clarify (and moving the zoom to current
function to another place).
The GIS Manager has no way of knowing that the data in the underlying vector
file has been changed. The normal display will only re-render a layer if it
has changed. This makes the display MUCH faster, but of course can be a
problem if you have changed the data in the layer by some means. Hence, the
new redraw all layers button.
This stuff will not be in the cvs until Monday when I'm back in the office.
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
From: Benjamin Ducke <benjamin.ducke@ufg.uni-kiel.de>
Date: Sun, 07 May 2006 19:41:44 +0200
To: GRASS devel <grass-dev@grass.itc.it>
Subject: [GRASS-dev] gis.m bugs
2. Changes done to a vector layer using v.digit do not show in
the Map Window, until one switches the Draw Mode
Michael Barton wrote:
The GIS Manager has no way of knowing that the data in the underlying vector
file has been changed. The normal display will only re-render a layer if it
has changed. This makes the display MUCH faster, but of course can be a
problem if you have changed the data in the layer by some means. Hence, the
new redraw all layers button.
At a minimum, gis.m should have an option to refresh a single layer
(i.e. discard any cached images for that layer).
Ideally, we need a g.timestamp module which returns the last-modified
time for a given entity (raster map, vector map, imagery group etc).
This essentially boils down to enumerating the files comprising a
given entity type (the details should already be present in g.remove
etc), obtaining the last-modified time for each, and returning the
most recent of those timestamps.
One possible complication: is there any way to determine when a vector
map was last modified? If not, this needs to be added; an empty file
which is updated whenever the vector map is modified should suffice
for most cases (obviously, we can't do anything about the user
manipulating the SQL database directly).
--
Glynn Clements <glynn@gclements.plus.com>