[GRASS-dev] can wxPython GUI handle order of options for v.type and alike?

Michael Barton michael.barton at asu.edu
Wed May 23 00:03:53 EDT 2007

On 5/22/07 2:44 PM, "Maciej Sieczka" <tutey at o2.pl> wrote:

> Hi
> I was wondering if the wxPython GUI is going to deal with problems the
> tcl/tk GUI can't - when there is a set of pre-defined parameters to
> choose from and the user should be able to decide about the order of them.
> An example is v.type [1], for which in the tcl/tk GUI you can specify
> the order of types only one way, eg. 'type=point,centroid', but
> 'type=centroid,point' is impossible to achieve.
> [1]http://intevation.de/rt/webrt?serial_num=2969
> Maciek

I agree that this is an annoying problem that makes v.type almost unusable
from the autogenerated GUI. wxPython as a platform won't inherently be able
to improve this, because the autogenerated dialogs can only display what is
included in the parser strings of the C-command. BUT... this is a very good
time to think of a better way to get this formatted in the C module so that
the dialogs generated in wxPython (and even TclTk) can be useable.

One suggestion that I have at the moment is that, instead of being coded so
that they end up as check boxes, the possible values for type (line,
boundary, etc) should not be coded as values and "type" should simply be a
text entry. Then the user can simply type in which combination she/he wants
(e.g., line,boundary).


Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

More information about the grass-dev mailing list