[GRASS5] pre2 nviz & darwin -- part ii

andy agena andya at mac.com
Sat Oct 27 10:24:21 EDT 2001

hi bob:

On Friday, October 26, 2001, at 07:27 PM, Bob Covill wrote:

> Andy,
> This sounds like a very unusual error. If I understand correctly, you
> cannot start nviz with the command "nviz -q".  You get the "already
> exists ..." error you mention above. That error sounds like TCL cannot
> address the window ID correctly. Are you running the session remotely
> (telnet, etc)? Also, you may want to check and see if there are any
> stale nviz's running. You can check this with something like "ps -aef |
> grep NVWISH2.2".

i'm running it locally.

there's something weird happening with xwindows.  when i 'grass5', 
there's some message that flashes briefly after choosing the location 
('xterm...').  do you get this as well jeshua? (though your machine is 
probably too fast to see it).  of course, i can't find where this 
message is logged, and it doesn't show up in the console (there is a 
message: "Warning: no access to tty (Inappropriate ioctl for device)." 
in the console).

Mapset <PERMANENT> in Location <spearfish>
GRASS 5.0.0pre2 > ps aux | grep nviz
andy   599   3.0  0.1     1112    196 std  R+     0:00.01 grep nviz

> If you have access to the program files you can edit the nviz tcltkgrass
> startup module to change the "el=" option you mention above. The file to
> edit is in $GISBASE/tcltkgrass/module and is entitled nviz. Simply
> change the option "el" to any other legal value (anything from "e" to
> "elevation"). You could also try these variations on the command line to
> see what is going on.

the contents of $GISBASE/tcltkgrass/module/nviz:

interface_build {
     {nviz} 1
     {Visualization tool.}
     {entry el {Name of existing raster map:} 0 raster}
     {entry ve {Name of existing vector map:} 0 vector
     {entry si {Name of existing sites map:} 0 sites}

which i changed to elevation, vector, and sites, respectively.  same 

any idea on where the weird 'xterm...' error might be logged?	

take care,

More information about the grass-dev mailing list