On 3/30/08 2:17 AM, "Glynn Clements" <[EMAIL PROTECTED]> wrote:
>> There is one place that is a serious problem where we could really
>> use a much more experienced TclTk programmer like you to sort out:
>> the progress bar. It seems like it ought to be straightforward, but
>> there is something wrong with the progress bar code so that if a
>> module executes too quickly, it crashes the entire TclTk interface.
>
> AFAICT, the issue is due to an event handler being re-entered through
> the "update" command.
>
> I note that ProgressBar::_modify calls update. One option is to remove
> that call. Any other options (i.e. allowing event handlers to be
> re-entered) are quite complex.
Now that I can compile again, I went to look for this to see if your
suggested remedy works. I can't find where you are talking about. Is this in
the GRASS code or in the TclTk code?
Michael
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
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
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
