Michael Barton 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?
It's at the bottom of lib/external/bwidget/progressbar.tcl. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
