[GRASS-SVN] r69230 - grass/trunk/misc/m.nviz.script

[svn_grass at osgeo.org]

Author: martinl
Date: 2016-08-23 05:46:27 -0700 (Tue, 23 Aug 2016)
New Revision: 69230

Modified:
   grass/trunk/misc/m.nviz.script/m.nviz.script.html
Log:
 <m.nviz.script> - old manuals? (see #3040)

Modified: grass/trunk/misc/m.nviz.script/m.nviz.script.html
===================================================================
--- grass/trunk/misc/m.nviz.script/m.nviz.script.html	2016-08-23 12:25:03 UTC (rev 69229)
+++ grass/trunk/misc/m.nviz.script/m.nviz.script.html	2016-08-23 12:46:27 UTC (rev 69230)
@@ -3,8 +3,7 @@
 The <em>m.nviz.script</em> program allows the user to easily create a script
 that can be run in NVIZ to fly through a terrain.
 
-The NVIZ flight path can be chosen interactively from the GRASS
-monitor (<em>-i</em>) or supplied on the command line as comma
+The NVIZ flight path can be supplied on the command line as comma
 separated coordinates. The program optionally allows a KeyFrame
 file to created (after running the script). This KeyFrame file can
 be loaded into the <em>Keyframe Animation</em> panel for fine
@@ -18,11 +17,6 @@
 
 <h3>Flags:</h3>
 <dl>
-<dt><b>-i</b>
-<dd>Intercative mode
-<dd>The user selects the camera path from the GRASS monitor by
-	clicking the left mouse button along the route. Click the
-	right mouse button to finish.
 <dt><b>-f</b>
 <dd>Full render
 <dd>The script will draw all loaded NVIZ data and save scene to PPM image.
@@ -75,7 +69,6 @@
 
 <dt><b>route</b>
 <dd>The comma separated geographic coordinates for keyframe locations.
-<dd>The interactive flag (<em>-i</em>) overrides this option.
 
 </dl>
 
@@ -87,7 +80,7 @@
 <div class="code"><pre>
 g.region raster=elevation.dem
 d.rast elevation.dem
-m.nviz.script -ik input=elevation.dem output=nviz.script dist=2400 ht=1220 frames=1000
+m.nviz.script -k input=elevation.dem output=nviz.script dist=2400 ht=1220 frames=1000
 </pre></div>
 In the above the example the user is prompted to select the route from the GRASS monitor.
 The output script, 'nviz.script.nvscr', can then be run in NVIZ: