Re: [GRASS-dev] [GRASS GIS] #2503: wxdigit: wrong undo redo

2014-12-10 Thread GRASS GIS
#2503: wxdigit: wrong undo  redo
--+-
  Reporter:  mlennert |   Owner:  grass-dev@…  
  Type:  defect   |  Status:  closed   
  Priority:  normal   |   Milestone:  7.0.0
 Component:  wxGUI| Version:  svn-trunk
Resolution:  fixed|Keywords:  digitizer
  Platform:  Unspecified  | Cpu:  Unspecified  
--+-

Comment(by mmetz):

 Replying to [comment:13 mlennert]:
 
  Just one question concerning r63398: shouldn't the code just be deleted
 instead of using 'if 0' ?

 I am not sure if the new PostGIS interface needs this, Martin would know
 more about this, therefore I deactivated the code instead of deleting the
 code. The same applies to the list of updated nodes (not used by the
 digitizer, but by the PostGIS functions in the vector lib, I think).

 Markus

-- 
Ticket URL: https://trac.osgeo.org/grass/ticket/2503#comment:14
GRASS GIS http://grass.osgeo.org

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

Re: [GRASS-dev] [GRASS GIS] #2503: wxdigit: wrong undo redo

2014-12-10 Thread GRASS GIS
#2503: wxdigit: wrong undo  redo
--+-
  Reporter:  mlennert |   Owner:  grass-dev@…  
  Type:  defect   |  Status:  closed   
  Priority:  normal   |   Milestone:  7.0.0
 Component:  wxGUI| Version:  svn-trunk
Resolution:  fixed|Keywords:  digitizer
  Platform:  Unspecified  | Cpu:  Unspecified  
--+-
Changes (by martinl):

 * cc: martinl (added)


-- 
Ticket URL: https://trac.osgeo.org/grass/ticket/2503#comment:15
GRASS GIS http://grass.osgeo.org

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

Re: [GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite

2014-12-10 Thread GRASS GIS
#2509: d.mon output overwrite
-+--
 Reporter:  martinl  |   Owner:  martinl
 Type:  defect   |  Status:  assigned   
 Priority:  normal   |   Milestone:  7.0.0  
Component:  Display  | Version:  unspecified
 Keywords:  d.mon|Platform:  Unspecified
  Cpu:  Unspecified  |  
-+--

Comment(by martinl):

 Summary: originally reported bug has been fixed in r63466 and related
 commits (r63467 and r63465).

 {{{
 ls map.png ; d.mon cairo
 map.png
 ERROR: option output: map.png exists.
 }}}

 {{{
 d.mon cairo --o
 WARNING: File 'map.png' already exists and will be overwritten
 Output file: /opt/src/grass_trunk/map.png
 }}}

-- 
Ticket URL: https://trac.osgeo.org/grass/ticket/2509#comment:7
GRASS GIS http://grass.osgeo.org

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


Re: [GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite

2014-12-10 Thread GRASS GIS
#2509: d.mon output overwrite
-+--
 Reporter:  martinl  |   Owner:  martinl
 Type:  defect   |  Status:  assigned   
 Priority:  normal   |   Milestone:  7.0.0  
Component:  Display  | Version:  unspecified
 Keywords:  d.mon|Platform:  Unspecified
  Cpu:  Unspecified  |  
-+--

Comment(by martinl):

 Replying to [comment:6 neteler]:

  I tried as well - must be display driver related of course. A rather
 annoying problem...

 yes, it comes from `D_close_driver()`, will look at it ASAP.

-- 
Ticket URL: https://trac.osgeo.org/grass/ticket/2509#comment:8
GRASS GIS http://grass.osgeo.org

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


[GRASS-dev] [GRASS GIS] #2510: v.db.addcolumn, bad parser syntax in script causes error, cascades to other modules

2014-12-10 Thread GRASS GIS
#2510: v.db.addcolumn, bad parser syntax in script causes error, cascades to 
other
modules
---+
 Reporter:  isaacullah |   Owner:  grass-dev@…  

 Type:  defect |  Status:  new  

 Priority:  major  |   Milestone:  7.0.0

Component:  Vector | Version:  svn-releasebranch70  

 Keywords:  parser, syntax, error, script  |Platform:  Linux

  Cpu:  x86-64 |  
---+
 Hi all,

 In latest version of 7 from GRASS stable Ubuntu PPA archive,
 v.db.addcolumn is broken because of a change to the parser code in the
 script. The error is:

 {{{
 ERROR: Sorry, map is not a valid parameter
 ERROR: Required parameter output not set:
 (Name for output vector map)
 }}}


 But this is because the only options are output, and map and layer
 don't show up. Looking at the script, I see that the relevant parser code
 in the header is this:

 {{{
 #%module
 #% description: Adds one or more columns to the attribute table connected
 to a given vector map.
 #% keywords: vector
 #% keywords: attribute table
 #% keywords: database
 #%end

 #%option G_OPT_V_MAP
 #%end

 #%option G_OPT_V_FIELD
 #% label: Layer number where to add column(s)
 #%end

 #%option
 #% key: columns
 #% type: string
 #% label: Name and type of the new column(s) ('name type [,name type,
 ...]')
 #% description: Data types depend on database backend, but all support
 VARCHAR(), INT, DOUBLE PRECISION and DATE
 #% required: yes
 #%end
 }}}

 It's obvious that it's the G_OPT_V_MAP and G_OPT_V_FIELD that are
 causing the error. I've not ever used that syntax in my own scripts (I
 wasn't aware that one *cold* do that, actually), but th error is fixed by
 changing to the normal parser syntax:

 {{{
 #%module
 #% description: Adds one or more columns to the attribute table connected
 to a given vector map.
 #% keywords: vector
 #% keywords: attribute table
 #% keywords: database
 #%end

 #%option
 #% key: map
 #% type: string
 #% gisprompt: old,vector,vector
 #% label: Name of map to add columns to the database
 #% required: yes
 #%end

 #%option
 #% key: layer
 #% type: integer
 #% label: Layer number where to add column(s)
 #% answer: 1
 #% required: yes
 #%end

 #%option
 #% key: columns
 #% type: string
 #% label: Name and type of the new column(s) ('name type [,name type,
 ...]')
 #% description: Data types depend on database backend, but all support
 VARCHAR(), INT, DOUBLE PRECISION and DATE
 #% required: yes
 #%end
 }}}

 Not sure if the v.db.addcolumn code was always like that, and the error is
 caused by some other change, or if this is due to a recent change to the
 script itself, but it seems like an easy fix. This is a serious bug
 because it breaks a lot of the other vector tools.

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/2510
GRASS GIS http://grass.osgeo.org

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

Re: [GRASS-dev] [GRASS GIS] #2510: v.db.addcolumn, bad parser syntax in script causes error, cascades to other modules

2014-12-10 Thread GRASS GIS
#2510: v.db.addcolumn, bad parser syntax in script causes error, cascades to 
other
modules
+---
 Reporter:  isaacullah  |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  major   |   Milestone:  7.0.0
Component:  Vector  | Version:  svn-releasebranch70  
 Keywords:  parser, v.db.addcolumn  |Platform:  Linux
  Cpu:  x86-64  |  
+---
Changes (by neteler):

  * keywords:  parser, syntax, error, script = parser, v.db.addcolumn


Comment:

 Replying to [ticket:2510 isaacullah]:
  Hi all,
 
  In latest version of 7 from GRASS stable Ubuntu PPA archive,
 v.db.addcolumn is broken because of a change to the parser code in the
 script. The error is:
 
  {{{
  ERROR: Sorry, map is not a valid parameter
  ERROR: Required parameter output not set:
(Name for output vector map)
  }}}

 Is it really the latest you are using there? We have made a major code
 cleanup, perhaps
 the package was created in the transition days?

 I just tried, works fine with the really current version:

 {{{
 GRASS 7.0.0svn (nc_spm_08_grass7):~  v.db.addcolumn random column=el102
 double precision
 GRASS 7.0.0svn (nc_spm_08_grass7):~  g.version -g
 version=7.0.0svn
 date=2014
 revision=63285M
 build_date=2014-12-03
 build_platform=x86_64-unknown-linux-gnu
 }}}

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/2510#comment:1
GRASS GIS http://grass.osgeo.org

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

Re: [GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite

2014-12-10 Thread GRASS GIS
#2509: d.mon output overwrite
-+--
 Reporter:  martinl  |   Owner:  martinl
 Type:  defect   |  Status:  assigned   
 Priority:  normal   |   Milestone:  7.0.0  
Component:  Display  | Version:  unspecified
 Keywords:  d.mon|Platform:  Unspecified
  Cpu:  Unspecified  |  
-+--

Comment(by martinl):

 Replying to [comment:6 neteler]:

   This might be something different but probably related. Call of
 `d.rast` when `d.mon wx0` is active causes creation of `map.png` in the
 current directory:
   I observe this for a long time already but until recently I wasn't
 able to find a cause.
 
  I tried as well - must be display driver related of course. A rather
 annoying problem...

 related to this issue something changed in display architecture (probably
 Glynn will know more), now you don't need to start any monitor to render
 data

 {{{
 d.mon -p
 No monitor selected

 d.vect streams --v
 Using display driver cairo...
 cairo: collecting to file 'map.png'
 cairo: image size 640x480
 Plotting...
 8554 lines plotted
 d.vect complete.
 }}}

 I would see this behaviour as misleading from the user point of view. In
 GRASS 7.0:

 {{{
 d.mon -p
 No monitor selected
 d.vect streams
 ERROR: No graphics device selected. Use d.mon to select graphics device.
 }}}

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/2509#comment:9
GRASS GIS http://grass.osgeo.org

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


Re: [GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite

2014-12-10 Thread GRASS GIS
#2509: d.mon output overwrite
-+--
 Reporter:  martinl  |   Owner:  martinl
 Type:  defect   |  Status:  assigned   
 Priority:  normal   |   Milestone:  7.0.0  
Component:  Display  | Version:  unspecified
 Keywords:  d.mon|Platform:  Unspecified
  Cpu:  Unspecified  |  
-+--

Comment(by martinl):

 Replying to [comment:9 martinl]:
  Replying to [comment:6 neteler]:
  related to this issue something changed in display architecture
 (probably Glynn will know more), now you don't need to start any monitor
 to render data

 it's r63361 (btw, the log doesn't explain why it bogus...). I really don't
 see the current behaviour of display commands in trunk as reasonable. The
 data are rendered automatically by default display driver without any
 noticing to the user. I strongly suggest to change it back as it works in
 G70 - to require to start any monitor - otherwise the user will very
 confused. As we are now.

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/2509#comment:10
GRASS GIS http://grass.osgeo.org

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


Re: [GRASS-dev] [GRASS GIS] #2258: t.create creates DB always in the PERMANENT

2014-12-10 Thread GRASS GIS
#2258: t.create creates DB always in the PERMANENT
-+--
 Reporter:  martinl  |   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  blocker  |   Milestone:  7.0.0
Component:  Temporal | Version:  svn-releasebranch70  
 Keywords:  t.register   |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--

Comment(by neteler):

 The doxygen documentation in lib/temporal/lib/default_name.c needs yet to
 be updated (I think).

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/2258#comment:20
GRASS GIS http://grass.osgeo.org

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

Re: [GRASS-dev] Dead code

2014-12-10 Thread Markus Neteler
Hi,

back to
http://grasswiki.osgeo.org/wiki/GRASS_7_ideas_collection#Dead_code_cleanup

how about moving
- r3.out.v5d, r3.in.v5d
- r3.mkdspf

to Addons?

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


Re: [GRASS-dev] GRASS 7 - Ubuntu package build problem on Launchpad

2014-12-10 Thread Markus Neteler
On Mon, Dec 8, 2014 at 10:11 PM, Ivan Mincik ivan.min...@gmail.com wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 I confirm that GRASS 7 is now building successfully in my PPA [1].

Excellent, thanks for your efforts!

 Somebody from GRASS team should request for build in GRASS PPA.

If still needed: I have a login there, what should I do? Sorry for
being without PPA experience...

But it seems to be done:
https://code.launchpad.net/~grass/+recipe/grass70-release

Markus


 1 - https://launchpad.net/~imincik/+archive/ubuntu/gis-dev/+packages


 - --
 Ivan Minčík
 ivan.min...@gmail.com  GPG: 0x79529A1E
 http://imincik.github.io/0x79529A1E.key
 ivan.min...@gista.sk GPG: 0xD714B02C
 http://imincik.github.io/0xD714B02C.key
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1

 iQEcBAEBAgAGBQJUhhPlAAoJEPfdLsR5UpoesFMIALlY9uvnkJXoZ0LaqWVd0raU
 /NGzUkJVA7bzILnmBAkGfdSCqKxhrztSBTSEM/A89WBoE4UIZJeUuyZHY45AXM+s
 psAAkC04jV4oy8xgodKGSpl9+wis1mImRDnIuZHBWnQIwpadh+aJEIW8dliUIpjU
 ReXrc2ZaHe27kfytnjxnh1YJ/dV/zMKyURaj7iEDhSC6t8Ycm+pmk1pseAmYrgHY
 J13ydatYhIEffn+LX5iaqSdXy8PrsnU2r93uJUtInv1ADgZfg4PTjhRraPTnOFY5
 OyAo5u3yTgiJNoPPBH2mWoUE3vpDJYXayA3mceZruIdZvMKFCIhe6n7w3eytMko=
 =oxe3
 -END PGP SIGNATURE-
 ___
 grass-dev mailing list
 grass-dev@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev