This is what I've done. For simplicity and to get it done fast, I've just sent the error to the terminal. A popup would be better in most cases, but a bit more work.
Michael On 8/24/07 3:27 PM, "Paul Kelly" <[EMAIL PROTECTED]> wrote: > Yes sorry I wasn't clear = I meant keeping the stderr output as well as > catching the error, and then something along the lines of displaying it in a > pop-up dialog to the user - if the program just failed then a pop-up dialog > would say that but if there was also an informational error message it would > be displayed in the pop-up and could be a valuable hint as to the source of > the problem. I did a bit of that in the recent changes I made to the way > g.proj was run in the background when creating a new location during the > gis_set.tcl startup - that's where the idea was coming from. __________________________________________ Michael Barton, Professor of Anthropology 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 _______________________________________________ grass-dev mailing list grass-dev@grass.itc.it http://grass.itc.it/mailman/listinfo/grass-dev
