[GRASS-dev] [GRASS GIS] #2848: g.gui.vdigit: snapping distance seems to only be defined in map units, not screen pixels

GRASS GIS trac at osgeo.org
Tue Sep 27 11:01:34 PDT 2016


#2848: g.gui.vdigit: snapping distance seems to only be defined in map units, not
screen pixels
--------------------------+---------------------------------
  Reporter:  mlennert     |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  major        |  Milestone:  7.0.5
 Component:  wxGUI        |    Version:  svn-releasebranch70
Resolution:               |   Keywords:  vector, digitize
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+---------------------------------

Comment (by mlennert):

 Replying to [comment:16 annakrat]:
 > Replying to [comment:15 mlennert]:
 > > Replying to [comment:14 annakrat]:
 > > > Replying to [comment:13 mlennert]:
 > > > > Replying to [comment:12 annakrat]:
 > > > > > OK, try r69580. First remove the snapping record in your
 settings file. Save it in trunk, and now open the dialog in older GRASS.
 Save it and open it again in trunk. If there are no problems, I will
 backport it.
 > > > >
 > > > > This seems to work, except: when I chose map units in trunk, I get
 the following in the settings file:
 > > > >
 > > > >
 > > > > {{{
 > > > > vdigit;snapping;units;screen pixels;value;25;unit;1
 > > > > }}}
 > > > >
 > > > > which looks a bit contradictory ('unit: 1' should be 'units: map
 units', or ?).
 > > > >
 > > >
 > > > That's correct, 'units' is the old name kept there for backwards
 compatibility, 'unit' is the new one (0 is screen pixels, 1 is map units).
 > >
 > > Yes, I understand that, but if 1 is map units, then why does the line
 contain 'units;screen pixels' and 'unit;1' ? Shouldn't it be 'units;map
 units' ?
 >
 > I don't care about the value of 'units' anymore, I am not trying to set
 it, I just kept them there so that the settings file can be read without
 error in old versions.

 Then things look pretty good for me. I just want to make sure we don't
 create a regression if we backport this fix this late before the release
 of 7.0.5.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2848#comment:17>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list