[GRASS5] GRASS module descriptions (3)

[Andreas Lange]

Hi,

Eric G . Miller wrote:
> 
> On Thu, Nov 23, 2000 at 12:08:49AM +0100, Andreas Lange wrote:
> > Hi Michel, Hi Jan-Oliver,
> >
> > Michel Wurtz wrote:
> > > I run a "simple" script to show what's happening (see below)
> > > and found the following infos :
> > >
> > > d.colors, d.pan, d.save, d.what.sites, d.zoom,
> > > Thoses commands give only the text help when a monitor is running
> > > Without a running monitor, they print the following error message :
> > > No graphics monitor has been selected for output.
> > > Please run "d.mon" to select a graphics monitor.
> >
> > I noticed this when implementing the testsuite. But i have no obvious
> > solution.
> 
> Probably they check for a monitor too soon (before the call to
> G_parser()).

The problem is that some modules need info from the R_pad structure to
include in the commandline options/choices. And you can only open the
R_driver if a monitor is running. 
I can not be more precise, look into the code for examples. 
But it should be possible for the module to exit(-1) after the
G_parser() is called. 

> 
> > > d.site.pg, d.vect.pg, d.what.r.pg, d.what.s.pg, d.what.v.pg,
> > > g.column.pg, g.stats.pg, g.table.pg, v.reclass.pg print :
> > > Please run g.select.pg to identify a current database.
> > >
> > > (I don't know what's happening with a selected database)
> 
> Same kind of thing as above. G_parser() should be called before doing
> anything else.


-- 
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas.Lange at Rhein-Main.de - A.C.Lange at GMX.net



---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'