Details Ticket 4319


Comment | Reply | Take | Resolve


Serial Number 4319
Subject d.m: can't display a raster if 'was found in more mapsets'
Area grass6
Queue grass
Requestors tutey@o2.pl
Owner none
Status open
Last User Contact Fri Jun 23 22:18:14 2006 (2 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Wed Jul 26 18:29:03 2006 (2 yr ago)
Created Fri Apr 21 12:15:45 2006 (2 yr ago)

Transaction History Ticket 4319


Fri, Apr 21 2006 12:15:45    Request created by guest  
Subject: d.m: can't display a raster if 'was found in more mapsets'

Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 2006-04-05

Hi

Trying to display a raster of a name which repeats in another mapset leads to
a following error and the raster is not displayed:



WARNING: 'cell/x' was found in more mapsets (also found in melio2).
WARNING: 'cell/x' was found in more mapsets (also found in melio2).
    while executing
"close $rt"
    (procedure "DmRaster::display" line 27)
    invoked from within
"DmRaster::display $node"
    ("raster" arm line 2)
    invoked from within
"switch $type {
        group {
            DmGroup::display $node
	}
	raster {
	    DmRaster::display $node
	}
	labels {
	    DmLabels::display $node
..."
    (procedure "Dm::display_node" line 6)
    invoked from within
"Dm::display_node $n"
    (procedure "DmGroup::display" line 11)
    invoked from within
"DmGroup::display "root" "
    (procedure "Dm::display" line 8)
    invoked from within
"Dm::display"
    ("uplevel" body line 1)
    invoked from within
"uplevel \#0 $cmd"
    (procedure "Button::_release" line 18)
    invoked from within
"Button::_release .mainframe.topf.tb0.bbox1.b0"
    (command bound to event)

Maciek
Fri, Jun 23 2006 21:51:53    Mail sent by mbarton  
This is a d.rast problem rather than a d.m problem. AFAIK, it shows the
correct map, but gives this warning. You can avoid it by specifying map@$MAPSET.
Fri, Jun 23 2006 22:17:42    Mail sent by msieczka  
> This is a d.rast problem rather than a d.m problem.

Why does d.m crash then instead of issuing a warning and displaying the map
from current mapset anyway, like d.rast does?

> You can avoid it by specifying map@$MAPSET.

Following d.rast behaviour as described above would be best, if possible. If
not, maybe d.m could do that for the user: add "@mapset" suffix to the map
name after the map is selected from the list or, if map name is typed in
manually in d.m, force the current mapset?.

Maciek
Fri, Jun 23 2006 22:18:14    Mail sent by msieczka  
> This is a d.rast problem rather than a d.m problem.

Why does d.m crash then instead of issuing a warning and displaying the map
from current mapset anyway, like d.rast does?

> You can avoid it by specifying map@$MAPSET.

Following d.rast behaviour as described above would be best, if possible. If
not, maybe d.m could do that for the user: add "@mapset" suffix to the map
name after the map is selected from the list or, if map name is typed in
manually in d.m, force the current mapset?.

Maciek
Wed, Jul 26 2006 18:29:03    User changed to tutey@o2.pl by msieczka  
Comment | Reply | Take | Resolve

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request