[GRASS-user] Re: [GRASS-dev] MS-Windows native GRASS

[Moritz Lennert]

On Thu, September 14, 2006 05:56, Huidae Cho wrote:
> Hi,
>
> I'm so excited to announce that I've just uploaded a package for
> MS-Windows native GRASS at http://geni.ath.cx/grass.html .  Rather than
> putting everything required for winGRASS in one huge package, I have
> prepared
> a batch file for automatic installation except for MinGW, MSys, and
> PostgreSQL, which are distributed as *.exe.  I hope it will make easy for
> anyone to install winGRASS.

Congratulations ! At first try, install didn't work (nothing installed
even though it said it did). I then realised that the wget package was not
downloaded correctly. After I downloaded it again, everything went very
smoothly.

>
> Please note that this first package is considered incomplete and
> requires more testing and bug fixing.

First impressions:

- had to add c:\mingw\bin in the PATH line of grass.bat, otherwise it
wouldn't find wish84

- cannot create new mapset, I get:

bad option "-permissions": must be -archive, -hidden, -longname,
-readonly, -shortname, or -system
bad option "-permissions": must be -archive, -hidden, -longname,
-readonly, -shortname, or -system
    while executing
"file attributes $mymapset/VAR -permissions u+rw,go+r"
    invoked from within
".frame0.frameNMS.third.button invoke"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke]"
    (procedure "tk::ButtonUp" line 24)
    invoked from within
"tk::ButtonUp .frame0.frameNMS.third.button
"
    (command bound to event)

- any reason why the command line prompt is called 'GRASS-GRID' ?

- great speed compared to cygwin/grass

- for some commands (e.g. query) a console window flashes up very briefly.
No real problem, just a bit annoying.

- displaying a map works fine, but once you have displayed it, you cannot
change any formatting (colors, type, etc) even if you erase the screen, it
always comes back the way it was the first time. This happens with vector,
chart and raster layers (after running r.colors) . If I open a new
display, I can display the map differently. Looks like the .ppm files are
not updated correctly, even though I can see that the d.vect command
changes in the output:

***output***
d.vect map=communes color=0:0:0 lcolor=0:0:0 fcolor=none display=shape
type=point,line,boundary,area icon=basic/x size=5 layer=1 lsize=8
xref=left yref=center llayer=1

g.pnmcomp in=3020.4.ppm,3020.3.ppm mask=3020.4.pgm,3020.3.pgm
opacity=1.00,1.00 background=255:255:255 width=644 height=484
out=3020.1.ppm

d.font romans

d.frame -e

d.frame -e

d.vect map=communes color=153:0:153 lcolor=0:0:0 fcolor=none display=shape
type=point,line,boundary,area icon=basic/x size=5 layer=1 lsize=8
xref=left yref=center llayer=1

g.pnmcomp in=3020.4.ppm,3020.3.ppm mask=3020.4.pgm,3020.3.pgm
opacity=1.00,1.00 background=255:255:255 width=644 height=484
out=3020.1.ppm
****/output****

- trying to display a thematic layer, I get :

can't read "_data(.gronsole.gronsole,4,donecmd)": no such element in array
can't read "_data(.gronsole.gronsole,4,donecmd)": no such element in array
    while executing
"set donecmd $_data($path,$ci,donecmd)"
    (procedure "Gronsole::done_command" line 3)
    invoked from within
"Gronsole::done_command $path $ci"
    (procedure "Gronsole::execout" line 25)
    invoked from within
"Gronsole::execout $path $cmd $ci Gronsole::execwait"
    (procedure "Gronsole::run_wait" line 6)
    invoked from within
"Gronsole::run_wait .gronsole.gronsole {d.vect.thematic -s map=communes
type=area column=COMCOD  layer=1 icon=basic/circle size=5  maxsize=20
nint=4 po..."
    ("eval" body line 1)
    invoked from within
"eval Gronsole::$cmd .gronsole.gronsole $args"
    (procedure ".gronsole.gronsole" line 1)
    invoked from within
"$gronsole run_wait $cmd gism"
    (procedure "run_panel" line 4)
    invoked from within
"run_panel $cmd"
    (procedure "GmCommonLayer::display_commands" line 28)
    invoked from within
"GmCommonLayer::display_commands $namespace $id [list $cmd]"
    (procedure "GmCommonLayer::display_command" line 2)
    invoked from within
"GmCommonLayer::display_command [namespace current] $id $cmd"
    (procedure "GmThematic::display" line 68)
    invoked from within
"GmThematic::display $node $mod"
    ("thematic" arm line 2)
    invoked from within
"switch $type {
        group {
            GmGroup::display $node $mod
		}
		raster {
			GmRaster::display $node $mod
		}
		labels {
			GmLabels::disp..."
    (procedure "GmTree::display_node" line 7)
    invoked from within
"GmTree::display_node $n $mod"
    (procedure "GmGroup::display" line 22)
    invoked from within
"GmGroup::display "root" $mod"
    (procedure "MapCanvas::runprograms" line 63)
    invoked from within
"MapCanvas::runprograms $mon [expr {$mymodified != 0}]"
    (procedure "MapCanvas::drawmap" line 38)
    invoked from within
"MapCanvas::drawmap $mon"
    (procedure "MapCanvas::display_server" line 9)
    invoked from within
"MapCanvas::display_server"
    ("after" script)

This is a great beginning. Thanks Huidae !

Moritz