Glynn, we tested it from both guis as well as from the command line. Same issue every time. Those variables are not getting read in at all.<br><br><div class="gmail_quote">On Tue, May 19, 2009 at 3:48 PM, Glynn Clements <span dir="ltr"><<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5"><br>
C Michael Barton wrote:<br>
<br>
> We've just encountered a strange change in the way the GRASS parser<br>
> interacts with BASH. It's not clear whether it's the parser, BASH, or<br>
> something else.<br>
><br>
> Previoiusly, if a GUI field was described as<br>
><br>
> #% type: string<br>
><br>
> ...whatever was entered was treated as a string, whether the entry was<br>
> an alphabetic character string ("mymap") or a numeral ("50"). When the<br>
> field was read, its value could be stored in a variable and then used.<br>
> So entering 50 in an entry field defined as string would produce "50"<br>
> when parsed.<br>
><br>
> Now, this doesn't seem to be the behavior of the parser and/or BASH.<br>
> If 50 or "50" is entered into a field defined as #% type: string, it<br>
> is ignored and the value of the parsed variable is empty, OR if there<br>
> is a default value the default is used-even if the default value is<br>
> numeric. So for the following entry from a BASH script..<br>
><br>
> #%option<br>
> #% key: myfield<br>
> #% type: string<br>
> #% description: A string field<br>
> #% required : yes<br>
><br>
> ...if 50 is entered, $GIS_OPT_MYFIELD is empty<br>
><br>
> If there is a default, as below...<br>
><br>
> #%option<br>
> #% key: myfield<br>
> #% type: string<br>
> #% description: A string field<br>
> #% required : yes<br>
> #% answer : 1.5<br>
><br>
> ... and 50 is entered, $GIS_OPT_MYFIELD is 1.5<br>
><br>
> I have not yet tested this on the Mac, but it is showing up in GRASS<br>
> 6.5 (of a couple weeks back) in Ubuntu ver. 9.<br>
><br>
> Has anyone else encountered this?<br>
<br>
</div></div>I can't see any changes to lib/gis/parser.c or general/g.parser which<br>
could have caused this.<br>
<br>
Are you testing this from the command line, or via one of the GUIs?<br>
<font color="#888888"><br>
--<br>
Glynn Clements <<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>><br>
</font></blockquote></div><br><br clear="all"><br>-- <br><br>Isaac I Ullah, M.A.<br><br>Archaeology PhD Student,<br>ASU School of Evolution and Social Change<br><br>Research Assistant,<br>Mediterranean Landscape Dynamics Project<br>
***************************************************<br><a href="mailto:isaac.ullah@asu.edu">isaac.ullah@asu.edu</a><br><a href="mailto:ullah@archaeologist.com">ullah@archaeologist.com</a><br><br><a href="http://www.public.asu.edu/~iullah">http://www.public.asu.edu/~iullah</a><br>
***************************************************<br>