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

[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 glynn):

 Replying to [comment:10 martinl]:

 > > 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...).

 It's bogus because there's simply no reason for that check to be there.
 Everything worked fine before someone mistakenly added it, and works fine
 now that it has been removed. The only consequence of that check was to
 generate an error for entirely valid usage.

 > I really don't see the current behaviour of display commands in trunk as
 reasonable.

 The current behaviour is exactly the same as the old behaviour before
 someone decided to try to reincarnate the "monitor" concept from prior
 versions and introduced a bug in the process.

 > 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.

 Just because someone managed to introduce a bug which went un-noticed for
 3 years, that doesn't make it correct behaviour. GRASS 7.0 hasn't been
 released yet, so there's no imperative for compatibility.

 To re-iterate: GRASS_RENDER_IMMEDIATE is not required for normal operation
 (generating image files). It isn't supposed to be required, it wasn't
 required until someone introduced a bug (probably because they thought
 that it was required), it is no longer required now that the bug has been
 fixed.

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