[GRASS-dev] gis.m in wingrass: using where clause in d.vect
causes error :can't read "_data(.gronsole.gronsole, 9,
donecmd)": no such element in array
michael.barton at asu.edu
Sun Oct 8 14:38:33 EDT 2006
Something along this line popped up in a Mac installation. I think it was a
colleague of William Kyngesburye, so I'm copying him here. In that case
there was something missing in the installation that finally turned out to
be the problem.
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
> From: Moritz Lennert <mlennert at club.worldonline.be>
> Date: Sun, 8 Oct 2006 10:30:22 +0200 (CEST)
> To: Hamish <hamish_nospam at yahoo.com>, <michael.barton at asu.edu>
> Cc: <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] gis.m in wingrass: using where clause in d.vect
> causes error :can't read "_data(.gronsole.gronsole,9, donecmd)": no such
> element in array
> On Sun, October 8, 2006 04:59, Hamish wrote:
>> Moritz Lennert wrote:
>>> Using a where clause in vector display in gis.m causes the following
>>> error under WinGRASS. Any suggestions ?
>>> (WinGRASS version 2006-09-17)
>>> can't read "_data(.gronsole.gronsole,9,donecmd)": no such element in
>>> array can't read "_data(.gronsole.gronsole,9,donecmd)": no such
>>> element in array
>>> while executing
>>> "set donecmd $_data($path,$ci,donecmd)"
>> also seen on Linux, GRASS versions 6.3 and 6.2-rc1 IF you put the
>> query in the "query cat values" box by mistake.
> I am not near a windows box right now, but I am quite positive that this
> is not the problem here. I entered the query in the where box, not the cat
> But I'll make sure tomorrow.
More information about the grass-dev