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

[GRASS GIS]

#2503: wxdigit: wrong undo & redo
-------------------------+--------------------------------------------------
 Reporter:  mlennert     |       Owner:  grass-dev@…              
     Type:  defect       |      Status:  new                      
 Priority:  normal       |   Milestone:  7.0.0                    
Component:  wxGUI        |     Version:  svn-trunk                
 Keywords:  digitizer    |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by mlennert):

 Replying to [comment:3 mmetz]:
 > Replying to [comment:2 mlennert]:
 > > Replying to [comment:1 mmetz]:
 > > > Replying to [ticket:2503 mlennert]:
 > > > > The undo and redo buttons in the digitizer (accessed via the Map
 Display) seem to work well for simple features, but as soon as I use tools
 like split line or similar, the results of undo and redo become somewhat
 arbitrary (at least to the innocent user).
 > > >
 > > > Please try r63265 (trunk) or r63266 (relbr70).
 > >
 > > Much better, thanks !
 > >
 > > There still is some confusion when one goes back one or two steps,
 then digitizes something else.
 >
 > The question is what should happen with the available redo steps if
 digitize something new after some undo steps. Eliminate the redo steps or
 insert the new changeset before the first redo step? This is handled by
 the wx digitizer, not the vector lib.

 I've tried three different programs (LibreOffice Writer, Inkscape and
 GIMP) and all discard these redo steps,i.e. when you do A, then B, then
 undo B, then do C, you cannot find B again.

 This seems to be the most intuitive behaviour to me.

 >
 > > When you then undo and redo again, the stack seems to be mixed between
 the different paths, sometimes leading to objects left on screen even when
 going all the way back to the last possible undo.
 >
 > It seems that a new changeset is appended after the last redo step if
 available, leading to a mix-up.
 >

 Yes.

 Moritz

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