Hi,
If no X11 monitor working, v.digit called via "Digitize map" button in
gis.m leads to an error [1], then monitor 0 pops up. Pressing "Digitize
map" once more opens monitor 1, v.digit starts - but in monitor 0.
gis.m freezes until I quit v.digit.
Another bug is that when you try to run v.digit on vector from another
mapset, you get an error [2], instead of the explanation:
"GRASS_INFO_WARNING(29617,1): A map which is not in the current mapset
cannot be opened for update."
[1]
child process exited abnormally
child process exited abnormally
while executing
"exec -- v.digit -n map=poziomice_ptln_rogow >& /dev/null"
("eval" body line 1)
invoked from within
"eval exec -- $cmd $args >& /dev/null"
(procedure "run" line 6)
invoked from within
"run v.digit -n map=$opt($id,1,vect)"
(procedure "GmVector::WorkOnVector" line 34)
invoked from within
"GmVector::WorkOnVector $sel 0"
("vector" arm line 2)
invoked from within
"switch $type {
raster {
Gm::xmon term r.digit
return
}
vector {
GmVector::WorkOnVector $sel 0
..."
(procedure "GmTree::vedit" line 16)
invoked from within
"GmTree::vedit"
("uplevel" body line 1)
invoked from within
"uplevel \#0 $cmd"
(procedure "Button::_release" line 18)
invoked from within
"Button::_release .mainframe.topf.tb1.bbox5.b0"
(command bound to event)
[2]
child killed: segmentation violation
child killed: segmentation violation
while executing
"exec -- v.digit -n map=huharaha@wlasnosc >& /dev/null"
("eval" body line 1)
invoked from within
"eval exec -- $cmd $args >& /dev/null"
(procedure "run" line 6)
invoked from within
"run v.digit -n map=$opt($id,1,vect)"
(procedure "GmVector::WorkOnVector" line 34)
invoked from within
"GmVector::WorkOnVector $sel 0"
("vector" arm line 2)
invoked from within
"switch $type {
raster {
Gm::xmon term r.digit
return
}
vector {
GmVector::WorkOnVector $sel 0
..."
(procedure "GmTree::vedit" line 16)
invoked from within
"GmTree::vedit"
("uplevel" body line 1)
invoked from within
"uplevel \#0 $cmd"
(procedure "Button::_release" line 18)
invoked from within
"Button::_release .mainframe.topf.tb1.bbox5.b0"
(command bound to event)
--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/
With respect to the first error, are you using the most recent version of
gis.m? I made some changes in how the button opens an x11 display on
Thursday or Friday.
I'll look to see if there is a way to trap the second error.
The fundamental problem, of course, is that v.digit needs to be re-written.
What I'm trying to do are temporary work-arounds to keep it reasonably
functional.
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: Maciek Sieczka <werchowyna@epf.pl>
Date: Sun, 7 May 2006 15:04:34 +0200
To: <grass-dev@grass.itc.it>
Cc: <michael.barton@asu.edu>, <cedricgrass@shockfamily.net>
Subject: v.digit in gis.m errors
Hi,
If no X11 monitor working, v.digit called via "Digitize map" button in
gis.m leads to an error [1], then monitor 0 pops up. Pressing "Digitize
map" once more opens monitor 1, v.digit starts - but in monitor 0.
gis.m freezes until I quit v.digit.
Another bug is that when you try to run v.digit on vector from another
mapset, you get an error [2], instead of the explanation:
"GRASS_INFO_WARNING(29617,1): A map which is not in the current mapset
cannot be opened for update."
[1]
child process exited abnormally
child process exited abnormally
while executing
"exec -- v.digit -n map=poziomice_ptln_rogow >& /dev/null"
("eval" body line 1)
invoked from within
"eval exec -- $cmd $args >& /dev/null"
(procedure "run" line 6)
invoked from within
"run v.digit -n map=$opt($id,1,vect)"
(procedure "GmVector::WorkOnVector" line 34)
invoked from within
"GmVector::WorkOnVector $sel 0"
("vector" arm line 2)
invoked from within
"switch $type {
raster {
Gm::xmon term r.digit
return
}
vector {
GmVector::WorkOnVector $sel 0
..."
(procedure "GmTree::vedit" line 16)
invoked from within
"GmTree::vedit"
("uplevel" body line 1)
invoked from within
"uplevel \#0 $cmd"
(procedure "Button::_release" line 18)
invoked from within
"Button::_release .mainframe.topf.tb1.bbox5.b0"
(command bound to event)
[2]
child killed: segmentation violation
child killed: segmentation violation
while executing
"exec -- v.digit -n map=huharaha@wlasnosc >& /dev/null"
("eval" body line 1)
invoked from within
"eval exec -- $cmd $args >& /dev/null"
(procedure "run" line 6)
invoked from within
"run v.digit -n map=$opt($id,1,vect)"
(procedure "GmVector::WorkOnVector" line 34)
invoked from within
"GmVector::WorkOnVector $sel 0"
("vector" arm line 2)
invoked from within
"switch $type {
raster {
Gm::xmon term r.digit
return
}
vector {
GmVector::WorkOnVector $sel 0
..."
(procedure "GmTree::vedit" line 16)
invoked from within
"GmTree::vedit"
("uplevel" body line 1)
invoked from within
"uplevel \#0 $cmd"
(procedure "Button::_release" line 18)
invoked from within
"Button::_release .mainframe.topf.tb1.bbox5.b0"
(command bound to event)
--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko
najlepsze z nich!
http://katalog.panoramainternetu.pl/
On Sun, 07 May 2006 07:02:02 -0700
Michael Barton <michael.barton@asu.edu> wrote:
With respect to the first error, are you using the most recent
version of gis.m? I made some changes in how the button opens an x11
display on Thursday or Friday.
Today's CVS (2006.05.07).
I'll look to see if there is a way to trap the second error.
The fundamental problem, of course, is that v.digit needs to be
re-written. What I'm trying to do are temporary work-arounds to keep
it reasonably functional.
That's understood.
Maciek
--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/