Re: [GRASS-dev] GRASS 6.4 release

[Martin Landa]

Hi,

2009/9/11 Michael Barton :

+1^10 for releasing GRASS 6.4.0 ;-)

[...]

> There may be another Windows issue, but I'm not sure. When trying to create
> a location from a georeferenced file in Windows XP, 2 student got the same
> error

I will be able to try to fix some Windows-related bugs later. My
Windows are completely broken after I have installed SP3, so I need to
reinstall the whole system. Thanks Microsoft for providing SP which
destroys working (almost) OS ;-)

Martin

-- 
Martin Landa  * http://gama.fsv.cvut.cz/~landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #748: Inconsistency (?) in GUI v.db.connect

[GRASS GIS]

#748: Inconsistency (?) in GUI v.db.connect
-+--
  Reporter:  pvanbosgeo  |   Owner:  martinl 
  Type:  defect  |  Status:  assigned
  Priority:  normal  |   Milestone:  6.4.0   
 Component:  wxGUI   | Version:  svn-develbranch6
Resolution:  |Keywords:  v.db.connect
  Platform:  Linux   | Cpu:  x86-64  
-+--
Changes (by martinl):

 * cc: grass-dev@lists.osgeo.org (added)
  * owner:  grass-dev@lists.osgeo.org => martinl
  * status:  new => assigned

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #748: Inconsistency (?) in GUI v.db.connect

[GRASS GIS]

#748: Inconsistency (?) in GUI v.db.connect
-+--
  Reporter:  pvanbosgeo  |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect  |  Status:  new  
  Priority:  normal  |   Milestone:  6.4.0
 Component:  wxGUI   | Version:  svn-develbranch6 
Resolution:  |Keywords:  v.db.connect 
  Platform:  Linux   | Cpu:  x86-64   
-+--
Changes (by martinl):

  * keywords:  => v.db.connect
  * component:  default => wxGUI

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #196: wxGUI interface hangs, when adding maps to display

[GRASS GIS]

#196: wxGUI interface hangs, when adding maps to display
---+
  Reporter:  rmatev|   Owner:  grass-dev@lists.osgeo.org
  Type:  defect|  Status:  reopened 
  Priority:  minor |   Milestone:  6.4.0
 Component:  wxGUI | Version:  6.3.0
Resolution:|Keywords:   
  Platform:  MSWindows XP  | Cpu:  x86-32   
---+
Comment (by martinl):

 Replying to [comment:4 cmbarton]:
 > I've just tested this on 6.4 and 6.5 svn with Mac OSX. I have no
 problems. No hanging with DEBUG=4 set. Is this still a problem for anyone
 else?

 yes,

 {{{
 g.gisenv set=DEBUG=5
 }}}

  * start wxGUI
  * add new vector map layer
  * display

 wxGUI stops responding because of amount of debug messages redirected to
 command output window.

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #196: wxGUI interface hangs, when adding maps to display

[GRASS GIS]

#196: wxGUI interface hangs, when adding maps to display
---+
  Reporter:  rmatev|   Owner:  grass-dev@lists.osgeo.org
  Type:  defect|  Status:  reopened 
  Priority:  minor |   Milestone:  6.4.0
 Component:  wxGUI | Version:  6.3.0
Resolution:|Keywords:   
  Platform:  MSWindows XP  | Cpu:  x86-32   
---+
Comment (by cmbarton):

 I've just tested this on 6.4 and 6.5 svn with Mac OSX. I have no problems.
 No hanging with DEBUG=4 set. Is this still a problem for anyone else?

 Michael

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #271: some tabs of command dialogs are too narrow

[GRASS GIS]

#271: some tabs of command dialogs are too narrow
---+
  Reporter:  msieczka  |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect|  Status:  new  
  Priority:  minor |   Milestone:  6.4.0
 Component:  wxGUI | Version:  svn-develbranch6 
Resolution:|Keywords:   
  Platform:  All   | Cpu:  All  
---+
Comment (by cmbarton):

 I cannot reproduce this on my Mac with the current 6.5 svn. Is it fixed on
 other platforms too?

 Michael

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #607: Spinboxes should be used for r.composite params

[GRASS GIS]

#607: Spinboxes should be used for r.composite params
--+-
  Reporter:  frankie  |   Owner:  grass-dev@lists.osgeo.org
  Type:  enhancement  |  Status:  closed   
  Priority:  minor|   Milestone:  6.5.0
 Component:  Tcl  | Version:  6.4.0 RCs
Resolution:  wontfix  |Keywords:   
  Platform:  Unspecified  | Cpu:  Unspecified  
--+-
Changes (by cmbarton):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 The wxpython interface and way of parsing GRASS command arguments is much
 more sophisticated than the much older one for TclTk. It would take a
 major rewrite of the venerable gui.tcl to add a lot of these new features
 and would probably also require that the tcltk output of g_parser be
 substantially improved (wxpython reads xml from g_parser). Given that we
 are switching interfaces after 6.4 or the 6.x series, I don't think that
 this is worth the effort.

 Michael

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #510: bad display in the Output window for r.report and r.stats with aspect maps.

[GRASS GIS]

#510: bad display in the Output window for r.report and r.stats with aspect 
maps.
--+-
  Reporter:  clerici  |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  major|   Milestone:  6.4.0
 Component:  Tcl  | Version:  6.4.0 RCs
Resolution:   |Keywords:   
  Platform:  All  | Cpu:  Unspecified  
--+-
Comment (by cmbarton):

 I can replicate this too with r.stats. It seems to happen if you have a
 lot of data. The gronsole.tcl is fairly mysterious code in places. My only
 guess is that this output window was not designed to handle that much data
 coming in at once and the formatting lags the data stream.

 Michael

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #462: Tcl interp->result deprecated

[GRASS GIS]

#462: Tcl interp->result deprecated
--+-
  Reporter:  neteler  |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  major|   Milestone:  6.4.0
 Component:  Tcl  | Version:  svn-develbranch6 
Resolution:   |Keywords:   
  Platform:  All  | Cpu:  All  
--+-
Comment (by cmbarton):

 Is this still an issue? We are only maintaining, not developing the TclTk
 GUI beyond GRASS 6.4 right? So can't it freeze with TclTk 8.5 and/or this
 patch?

 Michael

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #608: GIS.m: Lat/Lon support broken in Map Display zooms

[GRASS GIS]

#608: GIS.m: Lat/Lon support broken in Map Display zooms
--+-
  Reporter:  hamish   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  Tcl  | Version:  6.4.0 RCs
Resolution:   |Keywords:  gis.m, LL
  Platform:  All  | Cpu:  All  
--+-
Comment (by cmbarton):

 I'm not having any trouble with this using 6.4 compiled today (10
 September 2009). I get a message about not being able to stay in "explore"
 mode if you zoom out beyond the poles. But I can still zoom out and in and
 get a map. No errors. The only oddity was that once I zoomed out beyond
 the poles and tried to zoom in with a box, it centered the display in the
 wrong place. If I just clicked, it zoomed in OK.

 I'm doing this on a Mac.

 Michael

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #593: WinGRASS GIS.m: cannot select maps from mapset GUI

[GRASS GIS]

#593: WinGRASS GIS.m: cannot select maps from mapset GUI
---+
  Reporter:  hamish|   Owner:  marisn
  Type:  defect|  Status:  reopened  
  Priority:  critical  |   Milestone:  6.4.0 
 Component:  Tcl   | Version:  6.4.0 RCs 
Resolution:|Keywords:  wingrass gis.m
  Platform:  MSWindows XP  | Cpu:  x86-32
---+
Comment (by cmbarton):

 Works fine in GRASS 6.4 and 6.5 svn on Mac OS X.

 Michael

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #748: Inconsistency (?) in GUI v.db.connect

[GRASS GIS]

#748: Inconsistency (?) in GUI v.db.connect
+---
 Reporter:  pvanbosgeo  |   Owner:  grass-dev@lists.osgeo.org
 Type:  defect  |  Status:  new  
 Priority:  normal  |   Milestone:  6.4.0
Component:  default | Version:  svn-develbranch6 
 Keywords:  |Platform:  Linux
  Cpu:  x86-64  |  
+---
 For an existing vector layer I want to change the table linked to it.
 Opening v.db.connect GUI, under the optional tab, after selecting table
 name: the drop down list under 'Key column name' still shows the columns
 of the current table connected, not the table selected in the drop down
 list under 'Table name'

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS 6.4 release

[Michael Barton]

To follow up on a recent thread, I'm also in favor of trying to get  
6.4 released. I know of 2 major issues


1) v.delaunay is still badly broken 
2) nviz will not launch from the wxpython menu in Windows. Because  
this does launch from the Msys command line, I suspect that it is  
something in the wxpython code (perhaps menuform.py). I don't think  
this is the same as 


There may be another Windows issue, but I'm not sure. When trying to  
create a location from a georeferenced file in Windows XP, 2 student  
got the same error


r.in.gdal input=F:\Documentele mele\GIS DataBase\SRTM_ff03_p184r028.tif 
\SRTM_ff03_p184r028.tif output=GIS_Group title=S_Carpathians_Romania  
location=Romania_UTM

ERROR: region for current mapset is not set
run "g.region"

Both students were trying to import geotif SRTM files from the GLCF  
site. They were importing different files and I've never run into  
problems with files from this site before.


However, another student successfully imported a georeferenced geotif  
of an ASTER DEM from another site, and created a location in Windows  
Vista. Both were using the same GRASS 6.4RC5 binary.


Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

Phone: 480-965-6262
Fax: 480-965-7671
www: www.public.asu.edu/~cmbarton, http://csdc.asu.edu







___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #484: Cannot reload maps to wxnviz

[GRASS GIS]

#484: Cannot reload maps to wxnviz
---+
  Reporter:  cmbarton  |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect|  Status:  new  
  Priority:  major |   Milestone:  6.5.0
 Component:  wxGUI | Version:  svn-develbranch6 
Resolution:|Keywords:  wxnviz   
  Platform:  MacOSX| Cpu:  OSX/Intel
---+
Comment (by cmbarton):

 This issue is fixed in GRASS 6.4 and 6.5 but is still broken in GRASS 7.

 Michael

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #598: MacOS X / OpenGL and Wxpython incompatible

[GRASS GIS]

#598: MacOS X / OpenGL and Wxpython incompatible
-+--
  Reporter:  vince   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect  |  Status:  new  
  Priority:  normal  |   Milestone:  6.4.0
 Component:  NVIZ| Version:  svn-trunk
Resolution:  |Keywords:   
  Platform:  MacOSX  | Cpu:  OSX/Intel
-+--
Comment (by cmbarton):

 I have compiled GRASS 6.5 and 6.4 and it all works fine, including nviz
 and the wxpython 3D.

 Here is what works for me with the newest versions. Note that this is
 compiled in 64 bit. I'm using OS X 10.5.8, the current frameworks by
 William Kyngesburye, and Activstates TclTk 8.5 for aqua. Please check to
 see if this works for you too.

 Configure string:

 ./configure --with-freetype --with-freetype-
 includes="/Library/Frameworks/FreeType.framework/unix/include/freetype2
 /Library/Frameworks/FreeType.framework/unix/include" --with-freetype-
 libs=/Library/Frameworks/FreeType.framework/unix/lib --with-
 gdal=/Library/Frameworks/GDAL.framework/Programs/gdal-config --with-proj
 --with-proj-includes=/Library/Frameworks/PROJ.framework/unix/include
 --with-proj-libs=/Library/Frameworks/PROJ.framework/unix/lib --with-proj-
 share=/Library/Frameworks/PROJ.framework/Resources/proj --without-geos
 --with-jpeg-
 includes=/Library/Frameworks/UnixImageIO.framework/unix/include --with-
 jpeg-libs=/Library/Frameworks/UnixImageIO.framework/unix/lib --with-png-
 includes=/Library/Frameworks/UnixImageIO.framework/unix/include --with-
 png-libs=/Library/Frameworks/UnixImageIO.framework/unix/lib --with-tiff-
 includes=/Library/Frameworks/UnixImageIO.framework/unix/include --with-
 tiff-libs=/Library/Frameworks/UnixImageIO.framework/unix/lib --without-
 postgres --without-mysql --with-odbc --with-sqlite --with-sqlite-
 libs=/Library/Frameworks/SQLite3.framework/unix/lib --with-sqlite-
 includes=/Library/Frameworks/SQLite3.framework/unix/include --with-fftw-
 includes=/Library/Frameworks/FFTW3.framework/unix/include --with-fftw-
 libs=/Library/Frameworks/FFTW3.framework/unix/lib --with-x --with-cxx
 --with-opengl=aqua --without-readline --prefix=/Applications/GRASS
 --enable-macosx-app --with-python=/usr/bin/python-config --with-
 wxwidgets=/usr/local/lib/wxPython-unicode-2.8.9.2/bin/wx-config --with-
 tcltk-includes="/Library/Frameworks/Tcl.framework/Headers
 /Library/Frameworks/Tk.framework/Headers
 /Library/Frameworks/Tk.framework/PrivateHeaders" --with-macosx-
 archs="i386,x86_64"

  IMPORTANT: after configure, but BEFORE make, edit
 include/make/platform.make to change the line from

 TCLTKLIBS   =  -ltk   -ltcl

 to

 TCLTKLIBS = -framework Tcl -framework Tk

 then run make and sudo make install

 Michael

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [GRASS-user] g.manual tries to run C:\Program Files\Internet Exporer\iexplore (the 'L' is missing from 'Explorer')

[Colin Nielsen]

>From the two possible WinGrass command lines (either cmd.exe or msys)
the following command will open the html index and returns the
terminal:

cmd /c "rundll32 url.dll,OpenURL "file:///C:/Program
Files/GRASS-6-SVN/docs/html/full_index.html""

I incorporated this into g.manual in a bit of an ugly fashion (see
attached patch), it works perfectly for msys but not for cmd. For cmd
it doesn't open the html and it doesn't return the terminal.
Hopefullly someone else can finish the task.

-Colin


On Wed, Jul 29, 2009 at 6:28 AM, Glynn Clements
 wrote:
>
> Hamish wrote:
>
>> For GRASS_HTML_BROWSER, it is read in a number of contexts by e.g.
>> by g.manual shell script (6.x), g.manual python (7.x), wxGUI,
>> tcl/tk GUI, grass-run.bat, gui startups, ...
>>
>> so it needs to be both cross-platform, cross-language, and cross-
>> environment (msys vs dos). thus IMO the only portable solution will
>> be to store it in the OS's native FS format and have each client
>> code translate downstream as needed rather than guess that up
>> front.
>
> That's all well and good, but we still aren't making any progress on
> the original question, i.e. what must the specified program accept as
> an argument?
>
> Until that's know, developers don't know how to use it, and users
> don't know how to set it.
>
>> I find msys to be too large complex to simply say "msys does or
>> does not support this or that" as a blanket statement.
>
> By "MSys", I mean the port of bash.
>
> --
> Glynn Clements 
>
Index: scripts/g.manual/g.manual
===
--- scripts/g.manual/g.manual	(revision 39119)
+++ scripts/g.manual/g.manual	(working copy)
@@ -76,7 +76,12 @@
 if [ -z "$GRASS_VERBOSE" ] || [ "$GRASS_VERBOSE" -gt 1 ] ; then
 	g.message "Starting browser <$BROWSERNAME> for module $1..."
 fi
-"$GRASS_HTML_BROWSER" file://"$GRASS_DOC_BASE"/docs/html/$1.html
+#hack for windows
+	if [ "$OS" = "Windows_NT" ] ; then
+		cmd /c "rundll32 url.dll,OpenURL "file://"$GRASS_DOC_BASE"/docs/html/$1.html""
+	else
+		"$GRASS_HTML_BROWSER" file://"$GRASS_DOC_BASE"/docs/html/$1.html
+	fi
   fi
 }
 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #65: WinGRASS: Starting up gis.m & hangs (probably on g.region)

[GRASS GIS]

#65: WinGRASS: Starting up gis.m & hangs (probably on g.region)
---+
  Reporter:  pvbgis|   Owner:  grass-dev@lists.osgeo.org
  Type:  defect|  Status:  closed   
  Priority:  major |   Milestone:  6.3.1
 Component:  default   | Version:  6.3.0
Resolution:  fixed |Keywords:  wingrass 
  Platform:  MSWindows XP  | Cpu:  Unspecified  
---+
Changes (by cnielsen):

  * status:  reopened => closed
  * resolution:  => fixed

Comment:

 On the latest
 [http://grass.osgeo.org/grass64/binary/mswindows/native/WinGRASS-6.4.0SVN-
 r38959-1-Setup.exe 6.4.0svn-r38959] this problem is fixed.
 {{{
 g.gui tcltk &
 }}}
 Or:
 {{{
 g.gui wxpython &
 }}}
 both work when grass is opened with the msys icons. With the cmd window
 startup method, closing the GUI closes grass completely (no more terminal)
 so the problem doesn't exist here either.

 It may never have been fixed for the grass63 installer but it is
 deprecated now anyway so I'm marking this as fixed.

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #744: package.sh for compiling on windows

[GRASS GIS]

#744: package.sh for compiling on windows
--+-
  Reporter:  hellik   |   Owner:  cnielsen
  Type:  defect   |  Status:  closed  
  Priority:  normal   |   Milestone:  6.5.0   
 Component:  Compiling| Version:  svn-develbranch6
Resolution:  fixed|Keywords:  wingrass
  Platform:  MSWindows Vista  | Cpu:  Unspecified 
--+-
Changes (by hellik):

  * status:  assigned => closed
  * resolution:  => fixed

Comment:

 thanks for the added note!

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #744: package.sh for compiling on windows

[GRASS GIS]

#744: package.sh for compiling on windows
--+-
  Reporter:  hellik   |   Owner:  cnielsen
  Type:  defect   |  Status:  assigned
  Priority:  normal   |   Milestone:  6.5.0   
 Component:  Compiling| Version:  svn-develbranch6
Resolution:   |Keywords:  wingrass
  Platform:  MSWindows Vista  | Cpu:  Unspecified 
--+-
Changes (by cnielsen):

 * cc: grass-dev@lists.osgeo.org (added)
  * owner:  grass-dev@lists.osgeo.org => cnielsen
  * status:  new => assigned

Comment:

 Replying to [comment:3 hellik]:
 > thanks for updating the wiki!
 >
 > {{{
 > And comment out (by adding a # to the start of the line) to lines 83-85,
 e.g.:
 > #cp /c/mingw/bin/libgnurx-0.dll $OSGEO_ROOT_MSYS/bin
 > #cp /c/mingw/bin/libiconv-2.dll $OSGEO_ROOT_MSYS/bin
 > #cp /c/mingw/bin/libintl-8.dll $OSGEO_ROOT_MSYS/bin
 > }}}
 >
 > shouldn't this lines 87-89?
 >
 
http://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/mswindows/osgeo4w/package.sh#L87

 The line numbers are slightly different in the different branches
 (instructions were for
 
[http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/mswindows/osgeo4w/package.sh#L83
 releasebranch_6_4]), I've added a note to the Wiki to watch out for this.
 I could duplicate the instructions for each version with the correct line
 numbers but it seems a bit redundant.

 Can this ticket be considered resolved?

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #744: package.sh for compiling on windows

[GRASS GIS]

#744: package.sh for compiling on windows
--+-
  Reporter:  hellik   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  normal   |   Milestone:  6.5.0
 Component:  Compiling| Version:  svn-develbranch6 
Resolution:   |Keywords:  wingrass 
  Platform:  MSWindows Vista  | Cpu:  Unspecified  
--+-
Comment (by hellik):

 thanks for updating the wiki!

 {{{
 And comment out (by adding a # to the start of the line) to lines 83-85,
 e.g.:
 #cp /c/mingw/bin/libgnurx-0.dll $OSGEO_ROOT_MSYS/bin
 #cp /c/mingw/bin/libiconv-2.dll $OSGEO_ROOT_MSYS/bin
 #cp /c/mingw/bin/libintl-8.dll $OSGEO_ROOT_MSYS/bin
 }}}

 shouldn't this lines 87-89?
 
http://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/mswindows/osgeo4w/package.sh#L87

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #737: ZBulkLabeling don't work

[GRASS GIS]

#737: ZBulkLabeling don't work
---+
  Reporter:  torstenosgeo  |   Owner:  martinl
  Type:  defect|  Status:  closed 
  Priority:  normal|   Milestone:  6.4.0  
 Component:  wxGUI | Version:  6.4.0 RCs  
Resolution:  fixed |Keywords:  vector digitizer, ZBulkLabeling
  Platform:  Linux | Cpu:  x86-32 
---+
Changes (by martinl):

  * status:  assigned => closed
  * resolution:  => fixed

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #483: "return to previous zoom" brakes "zoom to selected map"

[GRASS GIS]

#483: "return to previous zoom" brakes "zoom to selected map"
---+
  Reporter:  msieczka  |   Owner:  martinl 
  Type:  defect|  Status:  closed  
  Priority:  major |   Milestone:  6.4.0   
 Component:  wxGUI | Version:  svn-develbranch6
Resolution:  fixed |Keywords:  raster querying 
  Platform:  Linux | Cpu:  x86-64  
---+
Changes (by martinl):

  * status:  assigned => closed
  * resolution:  => fixed

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #747: v.rast.stats to table connected to layer 2 fails

[GRASS GIS]

#747: v.rast.stats to table connected to layer 2 fails
-+--
 Reporter:  pvanbosgeo   |   Owner:  grass-dev@lists.osgeo.org
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  6.4.0
Component:  default  | Version:  svn-develbranch6 
 Keywords:   |Platform:  Linux
  Cpu:  Unspecified  |  
-+--
 I am using v.rast.stats, which works fine when using the default attribute
 table (layer 1). When however I specify the layer to which the table to be
 changes is connected to be layer 2 it goes wrong. Basically (1) the
 columns are added to the table linked to layer 1 instead of the table
 linked to layer 2 and (2) the columns remain empty.

 Best regards

 Paulo

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #746: v.out.ascii with column parameter: segfault

[GRASS GIS]

#746: v.out.ascii with column parameter: segfault
--+-
  Reporter:  neteler  |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  normal   |   Milestone:  6.4.0
 Component:  Vector   | Version:  6.4.0 RCs
Resolution:   |Keywords:   
  Platform:  Linux| Cpu:  x86-64   
--+-
Comment (by neteler):

 Replying to [comment:4 glynn]:
 > Various dbString functions expect the target value to have been
 initialised, but "value" is uninitialised. It needs to be initialised
 with:
 ...
 >
 > {{{
 > db_init_string(&value.s);
 > }}}

 Is attached patch ok?

 Markus

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] color tables

[Hamish]

Helena wrote:
> I often get a question why there aren't images of color tables
> in GRASS GUI along with their names. Is this technically feasible?
...
> I am thinking about adding them to the r.colors man page,

thumbnail images of the colortables now added in 6.5 and 7 svn
in the raster/r.colors/ dir.

I put Glynn's html insertion magic trick in the Makefile, but for now
it's commented out. Someone who knows those things better than I can
enable it.

script to (re)generate the images can be found on the Talk page of:
  http://grass.osgeo.org/wiki/Color_tables


Hamish

ps- I cleaned up the d.colortable rendering to make this easier.



  
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: How to add 3D without breaking script compatibility in v.edit? (Was: Re: [GRASS-dev] Patch to make v.edit partially 3D)

[Martin Landa]

Hi,

2009/9/9 Harri Kiiskinen :

>>> If someone feels this is useful, please feel free to apply the
>>> changes. I do not normally use svn for anything, so if there's a
>>> better way to do this thing, just let me know.
>>
>> committed to trunk (r39093) and devbr6 (r39094). One drawback is that
>> 'move' parameter requires 3rd coordinate also for 2D vectors...
>>
>
> Thanks! Yes, this change is incompatible with earlier versions of
> GRASS, and I do not like it, but could not find an obvious solution to

right, reverted in r39105 (devbr6).

> the problem. If there was a way to make the third coordinate
> optional (like key_desc="like x,y[,z]", which I don't think
> there is), that would be a solution. One way would be

This could be done in trunk, it requires changes in the parser.
Probably such changes will be not backported to devbr6.

> to introduce a new flag (like -z) to indicate 3D-operation, but in
> that case, I don't see how the command line could be 'pre-parsed' for
> this flag so that the 'move' parameter could be given the correct
> form. A third option would be to add a new parameter, something like

Hm, right it will not solve key_desc problem.

> 'move3' to provide 3D-coordinates.
>
> The same problem affects also the parameters 'coord', and 'bbox', and
> even more so, as both currently accept multiple pairs of coordinates.

I don't like this solution, but probably it is the only one reasonable
solution for grass65 since we don't expect changes in the parser.

> So the solution adopted now should be the same for these, later on. (A
> problem I'm tempted to pay some attention to, too, as v.edit
> 3D functionality would be of some use.)
>
> Perhaps the safest and most compatible way would actually be to
> introduce new parameters for single and multiple 3D coordinate
> triples? (In practice, addition of 'move3', 'coord3' and 'bbox3'.) Any
> comments? Suggestions?

I have no better idea for GRASS 6.5 (please correct me if you have
better one). In GRASS 7.0 it would be cool to change the parser to
support optional key_desc item, so x,y,[z] requires at least 2 or 3
items.

Martin

-- 
Martin Landa  * http://gama.fsv.cvut.cz/~landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev