Re: Progress gauge weirdity

At 02:51 PM 3/20/00 +0100, Hrvoje Niksic wrote: >This is weird. While the font-lock is running with the new progress >gauge things, events seem to be picked up. Even stranger, they get >picked up in the wrong order, and they fuck up the work of the >progress gauge. > >So, if I press `a b c' while font-lock is running, "cba" is inserted >into the buffer when the font-locking is done. Also, the warnings >buffer says: > > (42) (warning/warning) Error caught in `font-lock-pre-idle-hook' > >Andy, what could be going on? Have a look at dispatch-non-command-events, see if you think this could be causing this. This is called in the progress gauge code to force control to return to the XtApp loop so that widgets will redisplay, otherwise you only ever see the widget after everything has finished. I'm not sure about the force_event_pending stuff either. If anyone with a good handle on the event code could take a look I would be mighty grateful. andy -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd