[GRASS-dev] Re: [GRASS GIS] #678: wrong coordinates after zoom to named region

[GRASS GIS]

#678: wrong coordinates after zoom to named region
---+
  Reporter:  mlennert  |   Owner:  martinl 
  Type:  defect|  Status:  assigned
  Priority:  normal|   Milestone:  6.4.0   
 Component:  wxGUI | Version:  6.4.0 RCs   
Resolution:|Keywords:  named region
  Platform:  Linux | Cpu:  Unspecified 
---+
Comment (by martinl):

 Replying to [comment:3 martinl]:
 > Replying to [comment:2 mlennert]:
 > > No, behaviour is different, but still weird:
 > >
 > > - zoom to named region
 > > - draw line : line ends seem to jump to outside the current window
 >
 > seems to work for me, tested on relbr64 and trunk. What version,
 revision?

 still relevant?

-- 
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] #809: v.db.addtable consistently fails in winGrass

[GRASS GIS]

#809: v.db.addtable consistently fails in winGrass
--+-
  Reporter:  JonBall  |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  critical |   Milestone:  6.4.0
 Component:  Vector   | Version:  svn-releasebranch64  
Resolution:   |Keywords:  v.db.addtable, wingrass  
  Platform:  MSWindows Vista  | Cpu:  x86-64   
--+-
Comment (by hamish):

 Replying to [comment:21 hamish]:
 {{{
lib/db/dbmi_base/login.c
dbmi_base/login.c:  ret = sscanf(buf, "%[^ ] %[^ ] %[^ ] %[^ ]",
 dr, db, usr, pwd);
 }}}
 >
 > This one will fail if the database path or passwd has spaces in
 > it. In grass 6 this file is ~/.grasslogin6. In grass 7 it is in
 > ~/.grass7/dblogin.
 >
 >  - What this means is that Postgre, MySQL, etc will currently
 > fail on WinGrass unless the databases are installed in a dir
 > without spaces in them-
 ...
 > Because it is a different file for grass 7 we don't have to worry about
 transitioning. So I've gone ahead and converted that to use
 > "|" as the sep already.
 >
 > GRASS 6 will have to worry about forward/backward compatibility,
 > so needs the full G_tokenize() treatment like vector/MAP/dbln got.


 It turns out that db.login doesn't actually need a backend DB running to
 work, so is a bit easier to test.


 AFAICT the only solution is to ditch the existing grass 6 file format for
 ~/.grasslogin6 and replace it with one which uses '|' as the field
 separator. There is simply no way to tell the database path, username, and
 passwd apart if either the db or pw has spaces in it because the name and
 pw are optional. e.g.: Does the path have a single space in it or was the
 password omitted? No way to tell.

 the ~/.grasslogin6 format is:
 {{{
 driver  database path [ username [ passwd]]
 }}}

 where both name and pw are optional.


 IMO the lesser of evils is to change the fs to '|' now, and write in the
 release notes that you will have to re-login.

 A way to do this is to write a new .grasslogin64 file which contains the
 new format and leave any existing .grasslogin6 files alone (and ignored).
 This is my preferred option and in the interest of keeping the release
 schedule on track I've provisionally committed it to 6.5svn for evaluation
 & comment (r40369). It is the same as what is in trunk now, except for the
 .file name.


 Hamish

 ps- I backported the G_tokenize() fix for dbln to the 6.4rb earlier today.

-- 
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] #759: r.patch non-functional in WinGRASS 6.4 svn on Vista

[GRASS GIS]

#759: r.patch non-functional in WinGRASS 6.4 svn on Vista
--+-
  Reporter:  cmbarton |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  critical |   Milestone:  6.4.0
 Component:  Raster   | Version:  6.4.0 RCs
Resolution:   |Keywords:  r.patch, wingrass
  Platform:  MSWindows Vista  | Cpu:  Unspecified  
--+-
Comment (by hamish):

 Replying to [comment:16 glynn]:
 > Also, both of the cited bug reports relate to the msys.bat script,
 > which isn't relevant to GRASS' use of MSys.

 see mswindows/GRASS-Installer.nsi line 418 (etc.) and
 mswindows/README.html section 3.  The script is used, and those patches
 are incorporated.


 It occurs to me that if you put yourself in the mindset of MS Win world
 then putting so much trust into the file name is not so bizarre. After
 all, it's not such a great leap from resting so much trust on the contents
 of the last three letters of the filename, why not put meaning on the
 first 8+ as well? Not to defend it as very rational or nuthin, or a fit
 idea after ~1984 (or whenever the first Macintoshes came out), just
 saying.


 Hamish

-- 
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] #707: wxGUI: v.digit broken for new maps: "No vector map selected for editing." although selected

[GRASS GIS]

#707: wxGUI: v.digit broken for new maps: "No vector map selected for editing."
although selected
+---
  Reporter:  neteler|   Owner:  martinl 
  Type:  defect |  Status:  closed  
  Priority:  blocker|   Milestone:  6.4.0   
 Component:  wxGUI  | Version:  6.4.0 RCs   
Resolution:  duplicate  |Keywords:  vector digitizer, vdigit
  Platform:  Linux  | Cpu:  All 
+---
Comment (by micha):

 Hi Martin:
 Yes that seems to fix the prob. I removed the swig rpm (1.3.40) and
 compiled swig-1.4.36, then in grass I did: make clean, make, make install,
 and now the python vector digitizer works.
 Many thanks,
 Micha

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