Re: progress gauge weirdness

AP> At 09:38 PM 8/22/00 -0400, Jeff Miller wrote: AP> Although I have not see this it made me think about why it might AP> be happening and I found a logic error in the window config AP> code. Please update from CVS and see if it still occurs. cvs updated around 2300 GMT. I still get the problem, in fact, worse than with the patch you had sent before. AP> If it still occurs please recompile window.c with AP> BROKEN_SUBWINDOW_REDISPLAY defined and see if that fixes it. Tried this, and no effect. In fact, it doesn't seem to be related to size of the fontified buffer at all. I can just bring the small (3.1k) file into the (new xemacs) buffer and it triggers the remnant. I can bring the larger of the two files (420k) into a buffer and it doesn't trigger it at all. my crazy hypothesis: there is some crazy mix of characters in the uuencoded mess that is tripping up font lock and it bails. Perhaps some error condition occurs then that freaks out the progress gauge. i don't claim to know how that all interacts, but maybe font lock bails before the widget is fully realized? just my wild ass guess.... :-) jeff