[GRASS-dev] d.rast.edit in wxgrass

Michael Barton michael.barton at asu.edu
Thu Jun 14 16:10:11 EDT 2007




On 6/14/07 12:28 PM, "Glynn Clements" <glynn at gclements.plus.com> wrote:

>> If the command HAS arguments and IS a d.* command, it is added to the list
>> of display layers managed within render.py for the map display that has the
>> focus and the UpdateMap method is called to update that display. There is a
>> 2nd splitting that allows for multiple d.* commands to be separated by
>> semi-colons. This may or may not be a good idea in the end, but I thought
>> I'd see how it worked out.
> 
> This all looks suspiciously like DWIM, which is normally a bad thing
> for non-trivial systems.
> 

I don't think it is a DWIM. The normal CLI behavior currently is...

1) type a command without arguments and it (normally) opens a properties
dialog;

2) type a command with arguments and it runs the command. To run a d.*
command and have it do anything useful in the wxgrass environment, it needs
to be added to the list of display layers and the display updated. There is
no straightforward way to choose which of multiple open display windows
would show the d.* command results, so I'm simply picking the active one.
This can be changed by the user by simply clicking on a different display.

The added feature, which is particularly useful for running display commands
is the ability to 'chain' them together so you can create a display with
multiple overlaying maps. This is done here by separating d.* commands with
a semicolon. I'm not sure if this is the best way to achieve this end, but
it is convenient to have something along this line.

Michael

__________________________________________
Michael Barton, Professor of Anthropology and Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics and 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