[GRASS-dev] Re: [GRASS GIS] #74: Tcl version of v.digit's background colour doesn't work

#74: Tcl version of v.digit's background colour doesn't work +--- Reporter: craigleat | Owner: grass-dev@lists.osgeo.org Type: defect | Status: reopened Priority: minor | M

[GRASS-dev] Re: [GRASS GIS] #122: g.region should not duplicate the code of G3d_regionToCellHead ()

#122: g.region should not duplicate the code of G3d_regionToCellHead () --+- Reporter: 1gray| Owner: grass-dev@lists.osgeo.org Type: defect | Status: new Priority: trivial

[GRASS-dev] Re: [GRASS GIS] #117: r.digit: make guarantee_xmon fail nicely on WinGrass

#117: r.digit: make guarantee_xmon fail nicely on WinGrass -+-- Reporter: 4everskiff | Owner: grass-dev@lists.osgeo.org Type: defect | Status: new Priority: minor |

[GRASS-dev] Re: [GRASS GIS] #58: wx version of v.digit relies upon non-portable hacks

#58: wx version of v.digit relies upon non-portable hacks ---+ Reporter: marisn| Owner: martinl Type: defect| Status: assigned Priority: critical | Milestone: 6.4.0 C

[GRASS-dev] Re: [GRASS GIS] #80: Convert tcl grc to wxpython version

#80: Convert tcl grc to wxpython version --+- Reporter: dersh| Owner: martinl Type: enhancement | Status: assigned Priority: minor| Milestone: 6.4.0 Component: Python

[GRASS-dev] Re: [GRASS GIS] #80: Convert tcl grc to wxpython version

#80: Convert tcl grc to wxpython version --+- Reporter: dersh| Owner: martinl Type: enhancement | Status: closed Priority: minor| Milestone: 6.4.0 Component: Python

[GRASS-dev] r.infer, r.weight, r.combine vs r.mapcalc

Hello, Looking into the potential of using GRASS for multi-criteria analysis, I came upon Peter Löwe's article about r.infer in GRASS News Vol. 3 [1]. He also mentions r.weight and r.combine in the article (all from 5.4, never ported to 6.x). I'm not sure I completely understand what these th

Re: [GRASS-dev] Grass db abstraction

Sandeep, please take a look at: http://grass.osgeo.org/grass63/manuals/html63_user/helptext.html http://grass.osgeo.org/grass63/manuals/html63_user/databaseintro.html and http://download.osgeo.org/grass/grass6_progman/index.html -> GRASS DBMI DataBase Management Interface

Re: [GRASS-dev] Fixing progress bar crash in TclTk gui

Michael Barton wrote: > >> There is one place that is a serious problem where we could really > >> use a much more experienced TclTk programmer like you to sort out: > >> the progress bar. It seems like it ought to be straightforward, but > >> there is something wrong with the progress bar code s

Re: [GRASS-dev] Re: [GRASS GIS] #110: db/drivers/dbf fail to build due to undefined reference to 'SASetupDefaultHooks' (SHAPELIB)

GRASS GIS wrote: > Comment (by neteler): > > [please respond in trac, grass-dev cannot post to trac] Actually, I'd really prefer it if we could keep discussions on the mailing list. trac can be updated when issues get resolved. Right now, my grass-dev folder consists mostly of posts by "GRASS

Re: [GRASS-dev] Re: [GRASS GIS] #110: db/drivers/dbf fail to build due to undefined reference to 'SASetupDefaultHooks' (SHAPELIB)

Hi, not sure, I would prefer to follow trac ticket when responding. Mixing trac ticket comments with grass-dev ML is at the end quite messy and important notes could be missed when someone reads just trac ticket comments and doesn't follow grass-dev ML carefully. ;1 CZK Martin 2008/4/13, Glynn

Re: [GRASS-dev] Re: [GRASS GIS] #110: db/drivers/dbf fail to build due to undefined reference to 'SASetupDefaultHooks' (SHAPELIB)

On Sun, Apr 13, 2008 at 7:17 PM, Glynn Clements <[EMAIL PROTECTED]> wrote: > > GRASS GIS wrote: > > > Comment (by neteler): > > > > [please respond in trac, grass-dev cannot post to trac] > > Actually, I'd really prefer it if we could keep discussions on the > mailing list. trac can be updated wh

[GRASS-dev] Re: [GRASS trac] #90: v.parallel: problems with inside corners

#90: v.parallel: problems with inside corners --+- Reporter: hamish | Owner: grass-dev@lists.osgeo.org Type: defect | Status: new Priority: major| Milestone: 6.4.0

[GRASS-dev] trac management - was ticket #110

On Sun, Apr 13, 2008 at 9:00 PM, Markus Neteler <[EMAIL PROTECTED]> wrote: > On Sun, Apr 13, 2008 at 7:17 PM, Glynn Clements <[EMAIL PROTECTED]> > wrote: > > > GRASS GIS wrote: > > > > > Comment (by neteler): > > > > > > [please respond in trac, grass-dev cannot post to trac] > > > > Actually, I'

Re: [GRASS-dev] Re: [GRASS GIS] #110: db/drivers/dbf fail to build due to undefined reference to 'SASetupDefaultHooks' (SHAPELIB)

Markus Neteler wrote: > > > [please respond in trac, grass-dev cannot post to trac] > > > > Actually, I'd really prefer it if we could keep discussions on the > > mailing list. trac can be updated when issues get resolved. > > > The issue is (here) that eg Even Rouault (GDAL developer) who res

Re: [GRASS-dev] trac management - was ticket #110

Markus Neteler wrote: > I have taken liverty to change that. Now trac posts as: > > fromGRASS trac <[EMAIL PROTECTED]> <<- changed sender > reply-tograss-dev@lists.osgeo.org, > to undisclosed-recipients, > dateSun, Apr 13, 2008 at 9:05 PM

[GRASS-dev] trac management - was ticket #110

On Sun, Apr 13, 2008 at 9:54 PM, Glynn Clements <[EMAIL PROTECTED]> wrote: > Markus Neteler wrote: > > > > [please respond in trac, grass-dev cannot post to trac] > > > > > > Actually, I'd really prefer it if we could keep discussions on the > > > mailing list. trac can be updated when issues get

Re: [GRASS-dev] trac management - was ticket #110

Markus Neteler wrote: > > > > > [please respond in trac, grass-dev cannot post to trac] > > > > > > > > Actually, I'd really prefer it if we could keep discussions on the > > > > mailing list. trac can be updated when issues get resolved. > > > > > > > > > The issue is (here) that eg Even Rouaul

Re: [GRASS-dev] trac management - was ticket #110

On 14/04/08 01:00, Glynn Clements wrote: Since the web become popular, I've probably encountered hundreds of web-based communication systems (online "forums", bug trackers, etc). And in every single instance where I've tried to use them for an actual discussion (as opposed to: post a request,

Re: [GRASS-dev] r.infer, r.weight, r.combine vs r.mapcalc

Moritz Lennert wrote: > Looking into the potential of using GRASS for multi-criteria analysis, > I came upon Peter Löwe's article about r.infer in GRASS News Vol. 3 [1]. > He also mentions r.weight and r.combine in the article (all from 5.4, > never ported to 6.x). I'm not sure I completely under

Re: [GRASS-dev] trac management - was ticket #110

Markus: > > > For me threading works. The headers contain the relevant tags: Glynn: > > All responses are treated as replies to the original report, rather > > than as a reply to a specific message Markus: > OK, the same need to check trac modifications for a solution. note that within Trac you c

Re: [GRASS-dev] trac management - was ticket #110

Glynn: > Can the messages which trac sends to the list have the reporter's > address added to the To: or CC: fields? That way, they would normally > receive any follow-ups via email. note if you respond in the trac system you are automatically added to that bug's cc list. so "tourist" posters can

Re: [GRASS-dev] r.in.srtm doesn't validate zip file

Carlos wrote: > Hi, I just tried to import a srtm tile in grass 6.2.2 (gentoo-gis > overlay ebuild), and it didn't validated my .hgt.zip files. > > I checked in the script and it is checking against "file": > > # really a ZIP file? > if [ "`file -ib $FILE.hgt.zip`" != "application/x-zip" ] ; then