Details Ticket 2402


Comment | Reply | Take | Open


Serial Number 2402
Subject r.colors - new rules=name option not yet working
Area grass5.7
Queue grass
Requestors michael.barton@asu.edu
Owner none
Status resolved
Last User Contact Tue May 11 06:15:00 2004 (4 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Fri Oct 22 07:23:47 2004 (4 yr ago)
Created Mon May 10 07:04:20 2004 (4 yr ago)

Transaction History Ticket 2402


Mon, May 10 2004 07:04:20    Request created by guest  
Subject: r.colors - new rules=name option not yet working

I tried the new rules=[filename] option. It generates ERROR: Unable to open rules
file [filename]. 
Then it stops all processing until a ctrl-C is pressed. I tried a simple rules
file:

1 blue
2 green
end

(I tried it with and without 'end' and got the same result)

Also, it won't even get this far from the autogenerated GUI because it conflicts
with the type=[option]  
argument. There needs to be a 'none' selection for the type option in the GUI
header. 

Mon, May 10 2004 07:30:35    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Mon, 10 May 2004 17:30:19 +1200
From Hamish <hamish_nospam@yahoo.com>
To Request Tracker <grass-bugs@intevation.de>
Cc grass5@grass.itc.it
Subject Re: [GRASS5] [bug #2402] (grass) r.colors - new rules=name option not yet working
Message-Id <20040510173019.6040f697.hamish_nospam@yahoo.com>
In-Reply-To <20040510050420.4B67713B4C@lists.intevation.de>
References <20040510050420.4B67713B4C@lists.intevation.de>
X-Mailer Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-scanner scanned by Inflex 1.0.12.7
X-Spam-Status No, hits=-4.0 tagged_above=-999.0 required=3.0 tests=BAYES_00, FORGED_YAHOO_RCVD
X-Spam-Level
> this bug's URL: http://intevation.de/rt/webrt?serial_num=2402
> ---------------------------------------------------------------------
> Subject: r.colors - new rules=name option not yet working
> 
> I tried the new rules=[filename] option. It generates ERROR: Unable to
> open rules file [filename]. Then it stops all processing until a
> ctrl-C is pressed. I tried a simple rules file:
> 
> 1 blue
> 2 green
> end
> 
> (I tried it with and without 'end' and got the same result)

The rules file needs to be in the $GISBASE/etc/colors/ directory. I just
added a few more: terrain, bcyr, slope, and elevation. You can try
copying over the four example files from src/raster/r.colors/cmd/ as
well, some are nice.

 
> Also, it won't even get this far from the autogenerated GUI because it
> conflicts with the type=[option]  argument. There needs to be a 'none'
> selection for the type option in the GUI header. 

The GUI and man page will be updated at some point to cover both these
issues..


Hamish


Mon, May 10 2004 07:58:27    Mail sent by michael.barton@asu.edu  
Return-Path <michael.barton@asu.edu>
Delivered-To grass-bugs@lists.intevation.de
Mime-Version 1.0 (Apple Message framework v613)
In-Reply-To <20040510053035.5F2BC13B4C@lists.intevation.de>
References <20040510053035.5F2BC13B4C@lists.intevation.de>
Content-Type text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id <FEA1A5BD-A246-11D8-A9EB-000A956FE2E0@asu.edu>
Content-Transfer-Encoding 7bit
From Michael Barton <michael.barton@asu.edu>
Subject Re: [bug #2402] (grass) Transaction (hamish_nospam@yahoo.com)
Date Sun, 9 May 2004 22:58:01 -0700
To Hamish via RT <grass-bugs@intevation.de>
X-Mailer Apple Mail (2.613)
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
Hamish

Thanks much. That clarifies the use of rules=[filename] from the  
command line. I tried it and it worked great. I think it is an  
excellent addition. Now there needs to be an easy way to save a color  
table created via type=rules.

There is still a problem from the GUI. There is no way to 'turn off'  
the type= option so that r.colors will parse the rules= option.

Michael
____________________
C. Michael Barton, Professor
School of Human Origins, Cultures, & Societies
PO Box 872402
Arizona State University
Tempe, AZ  85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>
On May 9, 2004, at 10:30 PM, Hamish via RT wrote:

> this bug's URL: http://intevation.de/rt/webrt?serial_num=2402
>
> Mon, May 10 2004 07:30:35: Request 2402 was acted upon.
>
>  Transaction: Mail sent by hamish_nospam@yahoo.com
>
>        Queue: grass
>         Area: grass5.7
>      Subject: r.colors - new rules=name option not yet working
>        Owner:
>   Requestors: michael.barton@asu.edu
>       Status: open
>
> ----------------------------------------------------------------------- 
> --
>> this bug's URL: http://intevation.de/rt/webrt?serial_num=2402
>> ---------------------------------------------------------------------
>> Subject: r.colors - new rules=name option not yet working
>>
>> I tried the new rules=[filename] option. It generates ERROR: Unable to
>> open rules file [filename]. Then it stops all processing until a
>> ctrl-C is pressed. I tried a simple rules file:
>>
>> 1 blue
>> 2 green
>> end
>>
>> (I tried it with and without 'end' and got the same result)
>
> The rules file needs to be in the $GISBASE/etc/colors/ directory. I  
> just
> added a few more: terrain, bcyr, slope, and elevation. You can try
> copying over the four example files from src/raster/r.colors/cmd/ as
> well, some are nice.
>
>
>> Also, it won't even get this far from the autogenerated GUI because it
>> conflicts with the type=[option]  argument. There needs to be a 'none'
>> selection for the type option in the GUI header.
>
> The GUI and man page will be updated at some point to cover both these
> issues..
>
>
> Hamish
>
>
> --- Headers Follow ---
>
>> From hamish_nospam@yahoo.com  Mon May 10 07:30:34 2004
> Return-Path: <hamish_nospam@yahoo.com>
> Delivered-To: grass-bugs@lists.intevation.de
> Received: from mail.intevation.de (aktaia [212.95.126.10])
> 	by lists.intevation.de (Postfix) with ESMTP id 7557613941
> 	for <grass-bugs@lists.intevation.de>; Mon, 10 May 2004 07:30:34 +0200  
> (CEST)
> Received: from localhost (localhost [127.0.0.1])
> 	by mail.intevation.de (Postfix) with ESMTP id 59CA536E42
> 	for <grass-bugs@lists.intevation.de>; Mon, 10 May 2004 07:30:33 +0200  
> (CEST)
> Received: from mailhub1.otago.ac.nz (mailhub1.otago.ac.nz  
> [139.80.64.218])
> 	by mail.intevation.de (Postfix) with ESMTP id A91B236CE1
> 	for <grass-bugs@intevation.de>; Mon, 10 May 2004 07:30:31 +0200 (CEST)
> Received: (from root@localhost)
> 	by mailhub1.otago.ac.nz (8.12.11/8.12.11) id i4A5ULSe016405;
> 	Mon, 10 May 2004 17:30:21 +1200
> Received: from galadriel.otago.ac.nz (galadriel.otago.ac.nz  
> [139.80.64.213])
> 	by mailhub1.otago.ac.nz (8.12.11/8.12.9) with ESMTP id i4A5UKsj016377;
> 	Mon, 10 May 2004 17:30:20 +1200
> Received: from ocean3 (ocean3.otago.ac.nz [139.80.35.38])
> 	by galadriel.otago.ac.nz (8.12.8/8.12.8) with SMTP id i4A5UJmu026622;
> 	Mon, 10 May 2004 17:30:19 +1200 (NZST)
> Date: Mon, 10 May 2004 17:30:19 +1200
> From: Hamish <hamish_nospam@yahoo.com>
> To: Request Tracker <grass-bugs@intevation.de>
> Cc: grass5@grass.itc.it
> Subject: Re: [GRASS5] [bug #2402] (grass) r.colors - new rules=name  
> option
>  not yet working
> Message-Id: <20040510173019.6040f697.hamish_nospam@yahoo.com>
> In-Reply-To: <20040510050420.4B67713B4C@lists.intevation.de>
> References: <20040510050420.4B67713B4C@lists.intevation.de>
> X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-pc-linux-gnu)
> X-Face:  
> M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk! 
> HT&BB
>  8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
> Mime-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> X-scanner: scanned by Inflex 1.0.12.7
> X-Spam-Status: No, hits=-4.0 tagged_above=-999.0 required=3.0  
> tests=BAYES_00,
> 	FORGED_YAHOO_RCVD
> X-Spam-Level:
>
> -------------------------------------------- Managed by Request Tracker


Mon, May 10 2004 09:10:56    Mail sent by glynn.clements@virgin.net  
Return-Path <glynn.clements@virgin.net>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn.clements@virgin.net>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <16543.10886.296459.727653@cerise.nosuchdomain.co.uk>
Date Mon, 10 May 2004 08:08:54 +0100
To Request Tracker <grass-bugs@intevation.de>
Cc grass5@grass.itc.it
Subject Re: [GRASS5] [bug #2402] (grass) r.colors - new rules=name option not yet working
In-Reply-To <20040510050420.4B67713B4C@lists.intevation.de>
References <20040510050420.4B67713B4C@lists.intevation.de>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
Request Tracker wrote:

> this bug's URL: http://intevation.de/rt/webrt?serial_num=2402
> -------------------------------------------------------------------------
> 
> Subject: r.colors - new rules=name option not yet working
> 
> I tried the new rules=[filename] option. It generates ERROR: Unable to
> open rules file [filename].

Where [filename] is what? Does the file actually exist in the
$GISBASE/etc/colors directory?

> Then it stops all processing until a ctrl-C is pressed.

Actually, it pauses for 5 seconds after an error, then exits. Whether
it should pause is debatable.

> I tried a
> simple rules file:
> 
> 1 blue
> 2 green
> end
> 
> (I tried it with and without 'end' and got the same result)

Are you expecting rules= to read a rules file from the current
directory? Because that isn't what the rules= option is meant for. If
you want it to read your own rules file, use color=rules and shell
redirection e.g.:

	r.colors mapname color=rules < rulesfile

> Also, it won't even get this far from the autogenerated GUI because it
> conflicts with the type=[option] argument. There needs to be a 'none'
> selection for the type option in the GUI header.

It needs to be a separate menu entry; exactly the same issue also
applies to the rast= option.

-- 
Glynn Clements <glynn.clements@virgin.net>


Mon, May 10 2004 13:26:58    Mail sent by neteler@itc.it  
Return-Path <neteler@itc.it>
Delivered-To grass-bugs@lists.intevation.de
Date Mon, 10 May 2004 13:28:38 +0200
From Markus Neteler <neteler@itc.it>
To Hamish <hamish_nospam@yahoo.com>
Cc Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
Subject Re: [GRASS5] [bug #2402] (grass) r.colors - new rules=name option not yet working
Message-ID <20040510112838.GC18002@thuille.itc.it>
Mail-Followup-To Hamish <hamish_nospam@yahoo.com>, Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
References <20040510050420.4B67713B4C@lists.intevation.de> <20040510173019.6040f697.hamish_nospam@yahoo.com>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
In-Reply-To <20040510173019.6040f697.hamish_nospam@yahoo.com>
User-Agent Mutt/1.4.1i
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
On Mon, May 10, 2004 at 05:30:19PM +1200, Hamish wrote:
> > this bug's URL: http://intevation.de/rt/webrt?serial_num=2402
> > ---------------------------------------------------------------------
> > Subject: r.colors - new rules=name option not yet working
> > 
> > I tried the new rules=[filename] option. It generates ERROR: Unable to
> > open rules file [filename]. Then it stops all processing until a
> > ctrl-C is pressed. I tried a simple rules file:
> > 
> > 1 blue
> > 2 green
> > end
> > 
> > (I tried it with and without 'end' and got the same result)
> 
> The rules file needs to be in the $GISBASE/etc/colors/ directory. 

I have added the path to the message. Now the user knows where
the file is searched:

r.colors N45E008.meters rules=test.rul
ERROR: Unable to open rules file test.rul in
       /nfsmnt/ssi0/ssi/neteler/grass57/dist.i686-pc-linux-gnu/etc/colors/test.rul
> I just added a few more: terrain, bcyr, slope, and elevation. You can try
> copying over the four example files from src/raster/r.colors/cmd/ as
> well, some are nice.

Fixed also in 5.7 now.

> > Also, it won't even get this far from the autogenerated GUI because it
> > conflicts with the type=[option]  argument. There needs to be a 'none'
> > selection for the type option in the GUI header. 
> 
> The GUI and man page will be updated at some point to cover both these
> issues..

Left to the author :-)
On command line it's functional now in 5.7.

Markus


Mon, May 10 2004 13:33:11    Mail sent by neteler@itc.it  
Return-Path <neteler@itc.it>
Delivered-To grass-bugs@lists.intevation.de
Date Mon, 10 May 2004 13:34:53 +0200
From Markus Neteler <neteler@itc.it>
To Glynn Clements <glynn.clements@virgin.net>
Cc Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
Subject Re: [GRASS5] [bug #2402] (grass) r.colors - new rules=name option not yet working
Message-ID <20040510113453.GD18002@thuille.itc.it>
Mail-Followup-To Glynn Clements <glynn.clements@virgin.net>, Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
References <20040510050420.4B67713B4C@lists.intevation.de> <16543.10886.296459.727653@cerise.nosuchdomain.co.uk>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
In-Reply-To <16543.10886.296459.727653@cerise.nosuchdomain.co.uk>
User-Agent Mutt/1.4.1i
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
On Mon, May 10, 2004 at 08:08:54AM +0100, Glynn Clements wrote:
...
> > Also, it won't even get this far from the autogenerated GUI because it
> > conflicts with the type=[option] argument. There needs to be a 'none'
> > selection for the type option in the GUI header.
> 
> It needs to be a separate menu entry; exactly the same issue also
> applies to the rast= option.

What about a function which reports the names of the currently
existing files in $GISBASE/etc/colors/ ? A function which
returns the file names as comma separated list? Then
the 5.7 GUI would auto-generate a selection box, and the cmd
line version would show the names (so no further blind guessing).

Markus


Mon, May 10 2004 17:16:26    Mail sent by michael.barton@asu.edu  
Return-Path <michael.barton@asu.edu>
Delivered-To grass-bugs@lists.intevation.de
In-Reply-To <20040510113311.3EE11139B8@lists.intevation.de>
References <20040510113311.3EE11139B8@lists.intevation.de>
Mime-Version 1.0 (Apple Message framework v613)
Content-Type text/plain; charset=US-ASCII; format=flowed
Message-Id <FB0BF126-A294-11D8-A9EB-000A956FE2E0@asu.edu>
Content-Transfer-Encoding 7bit
Cc grass5@grass.itc.it
From Michael Barton <michael.barton@asu.edu>
Subject Re: [bug #2402] r.colors in GRASS 5.7
Date Mon, 10 May 2004 08:16:15 -0700
To Markus Neteler via RT <grass-bugs@intevation.de>
X-Mailer Apple Mail (2.613)
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
This sounds good.

Michael

____________________
C. Michael Barton, Professor
School of Human Origins, Cultures, & Societies
PO Box 872402
Arizona State University
Tempe, AZ  85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>
On May 10, 2004, at 4:33 AM, Markus Neteler via RT wrote:

> On Mon, May 10, 2004 at 08:08:54AM +0100, Glynn Clements wrote:
> ...
>>> Also, it won't even get this far from the autogenerated GUI because 
>>> it
>>> conflicts with the type=[option] argument. There needs to be a 'none'
>>> selection for the type option in the GUI header.
>>
>> It needs to be a separate menu entry; exactly the same issue also
>> applies to the rast= option.
>
> What about a function which reports the names of the currently
> existing files in $GISBASE/etc/colors/ ? A function which
> returns the file names as comma separated list? Then
> the 5.7 GUI would auto-generate a selection box, and the cmd
> line version would show the names (so no further blind guessing).
>
> Markus
>


Tue, May 11 2004 04:12:21    Mail sent by glynn.clements@virgin.net  
Return-Path <glynn.clements@virgin.net>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn.clements@virgin.net>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <16544.10406.713792.672565@cerise.nosuchdomain.co.uk>
Date Tue, 11 May 2004 02:13:10 +0100
To Markus Neteler <neteler@itc.it>
Cc Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
Subject Re: [GRASS5] [bug #2402] (grass) r.colors - new rules=name option not yet working
In-Reply-To <20040510113453.GD18002@thuille.itc.it>
References <20040510050420.4B67713B4C@lists.intevation.de> <16543.10886.296459.727653@cerise.nosuchdomain.co.uk> <20040510113453.GD18002@thuille.itc.it>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
Markus Neteler wrote:

> > > Also, it won't even get this far from the autogenerated GUI because it
> > > conflicts with the type=[option] argument. There needs to be a 'none'
> > > selection for the type option in the GUI header.
> > 
> > It needs to be a separate menu entry; exactly the same issue also
> > applies to the rast= option.
> 
> What about a function which reports the names of the currently
> existing files in $GISBASE/etc/colors/ ? A function which
> returns the file names as comma separated list?

The problem here is that the list could grow rather quickly now that
it can be extended without having to write any code.

-- 
Glynn Clements <glynn.clements@virgin.net>


Tue, May 11 2004 04:12:24    Mail sent by glynn.clements@virgin.net  
Return-Path <glynn.clements@virgin.net>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn.clements@virgin.net>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <16544.10226.153369.173328@cerise.nosuchdomain.co.uk>
Date Tue, 11 May 2004 02:10:10 +0100
To Markus Neteler <neteler@itc.it>
Cc Hamish <hamish_nospam@yahoo.com>, Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
Subject Re: [GRASS5] [bug #2402] (grass) r.colors - new rules=name option not yet working
In-Reply-To <20040510112838.GC18002@thuille.itc.it>
References <20040510050420.4B67713B4C@lists.intevation.de> <20040510173019.6040f697.hamish_nospam@yahoo.com> <20040510112838.GC18002@thuille.itc.it>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
Markus Neteler wrote:

> > > Subject: r.colors - new rules=name option not yet working
> > > 
> > > I tried the new rules=[filename] option. It generates ERROR: Unable to
> > > open rules file [filename]. Then it stops all processing until a
> > > ctrl-C is pressed. I tried a simple rules file:
> > > 
> > > 1 blue
> > > 2 green
> > > end
> > > 
> > > (I tried it with and without 'end' and got the same result)
> > 
> > The rules file needs to be in the $GISBASE/etc/colors/ directory. 
> 
> I have added the path to the message. Now the user knows where
> the file is searched:
> 
> r.colors N45E008.meters rules=test.rul
> ERROR: Unable to open rules file test.rul in
>        /nfsmnt/ssi0/ssi/neteler/grass57/dist.i686-pc-linux-gnu/etc/colors/test.rul
This is the wrong solution; a user doesn't need this information. A
better solution would be to list the set of valid options. If the list
was constructed and set as opt4->options, G_parser() would do this
automatically; however, the list could easily become quite large.

The original problem seems to stem from the user thinking that rules=
was meant for using user-supplied rule files. It isn't; color=rules
and shell redirection is the correct solution in that case. I'll fix
that problem by removing the word "file" from the option's
description, e.g.

    opt4->description = "name of predefined rule set";

rules= is meant to be analogous to color=, and may well be eliminated
in future (i.e. rules= will be renamed to color=). I just didn't want
to mess up the existing color= behaviour until the new code had some
testing and the "exceptions" (i.e. color=grey.eq/grey.log/random/rules)
had been dealt with.

-- 
Glynn Clements <glynn.clements@virgin.net>


Tue, May 11 2004 06:15:00    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Tue, 11 May 2004 16:14:43 +1200
From Hamish <hamish_nospam@yahoo.com>
To Glynn Clements <glynn.clements@virgin.net>
Cc neteler@itc.it, grass-bugs@intevation.de, grass5@grass.itc.it
Subject Re: [GRASS5] [bug #2402] (grass) r.colors - new rules=name option not yet working
Message-Id <20040511161443.3705f643.hamish_nospam@yahoo.com>
In-Reply-To <16544.10406.713792.672565@cerise.nosuchdomain.co.uk>
References <20040510050420.4B67713B4C@lists.intevation.de> <16543.10886.296459.727653@cerise.nosuchdomain.co.uk> <20040510113453.GD18002@thuille.itc.it> <16544.10406.713792.672565@cerise.nosuchdomain.co.uk>
X-Mailer Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-scanner scanned by Inflex 1.0.12.7
X-Spam-Status No, hits=-4.0 tagged_above=-999.0 required=3.0 tests=BAYES_00, FORGED_YAHOO_RCVD
X-Spam-Level
> > > > Also, it won't even get this far from the autogenerated GUI
> > > > because it conflicts with the type=[option] argument. There
> > > > needs to be a 'none' selection for the type option in the GUI
> > > > header.
> > > 
> > > It needs to be a separate menu entry; exactly the same issue also
> > > applies to the rast= option.
> > 
> > What about a function which reports the names of the currently
> > existing files in $GISBASE/etc/colors/ ? A function which
> > returns the file names as comma separated list?
> 
> The problem here is that the list could grow rather quickly now that
> it can be extended without having to write any code.


I don't see this as a big problem if the default install is limited to
a dozen or so default color scales (we shouldn't be drowning the users
with many like options IMO).

If someone wants to install 200 custom rules files, they get to deal
with the consequences... same as if they installed 200 TT fonts on their
computer.


Perhaps we should add a -l flag to list available rules? Then the
default help page/parser stays clean.


see 'g.mapsets -l'


Hamish


Fri, Oct 22 2004 07:23:47    Status changed to resolved by hbowman  
Fri, Oct 22 2004 07:23:47    Comments added by hbowman  
rules=bad now produces an informative error message.

GUI seems to work.

'r.colors -l' lists available rules.


another bug closed.


Hamish
Comment | Reply | Take | Open

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request