> One thing I miss in the new GUI of GRASS 5.7 that I have in GRASS
> 5.03: The little blue text saying "Running..." and "Finished". It
> was really usefull and now it is sometimes difficult to know if a
> command is still busy or has already finished. (This is especially
> true for a newbie when I have no idea how long a command would
> normally run at different resolutions).This is something generated (or not) within each command module. Some
of them have it in GRASS 5.7. Most of the scripts I've written or
updated from GRASS 5.3 to 5.7 print a message when they are done.
Sometimes it doesn't really matter and other times it is very helpful.
This should really be in G_parser() or G_gui(), not in every module.
Problem is, the module is started with "&" so the Tcl script doesn't
know when it finished. Also the module is started from the Tcl with >1
parameter, so a argv==0 test doesn't help. I could get it to work if I
wrote to stdout before launching G_gui() [*], but then it would put
"Finished." in the wrong place when you ran it from the command line.
[*] stderr is written immediately into the tcl window;
stdout after the module has finished (e.g. r.profile).
What is most annoying to me are those older commands that send an
email message when they are completed. Of course these go to an
internal mail system and never reaches the email I normally look at.
Periodically I look up how to get these messages. Then, because I
rarely use this, I promptly forget it.
grepping through the 5.7 source:
imagery/i.rectify/exec.c
imagery/i.rectify/mail.c
imagery/i.rectify/report.c
imagery/i.ortho.photo/photo.rectify/exec.c
imagery/i.ortho.photo/photo.rectify/mail.c
imagery/i.ortho.photo/photo.rectify/rectify.c
imagery/i.ortho.photo/photo.rectify/report.c
lib/gis/error.c
Hamish