#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 neteler): Replying to [comment:15 glynn]: > > However, the monitor concept is essential also for GRASS 7. At least for power users who stick to the command line. > > Why? Someone who "sticks to the command line" won't even have wxGUI running, in which case d.mon etc don't do anything for them. OK, then let's call it a "hybrid use mode": Doing everything from command line including opening and closing the wx0/wxN monitor and displaying. Just for map queries and zooming it is handy to use the mouse as in GRASS 6. > > The current behaviour of d.* to silently write into a PNG file is unhelpful. > > Yet, that's how those commands behaved since the display system was re- written. Maybe that was the idea but for sure not clearly communicated or implemented in all d.* modules. > I don't recall any discussion about the behaviour; it got changed by accident and now that's how it's "supposed" to be? When did we agree to this change, and why? Now which change? I just asked that the d.* modules please say what they do since I don't check the file system for a new file every time I issue a command. If it matters, more people are interested in a working d.mon/command line approach: see #1719,#2233, #2234 and many email discussions in the mailing lists (or http://gis.stackexchange.com/questions/71124/is-d-mon-xn- deprecated-in-grass-in-favor-of-something-in-the-wxgui or elsewhere). -- Ticket URL: <http://trac.osgeo.org/grass/ticket/2509#comment:16> GRASS GIS <http://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev