Hmmmmm. I've discovered that a single press of a cursor key leads to: expose 633x752+0+0 paint 633x752+0+0 work_area_handler, recevied X11 expose event 633x752+37+67 paint 633x752+0+0
XScreen::expose posts an XEvent that is received by the second call to XWorkArea::paint. It's able, therefore, to only draw the subrectangle it's requested to draw. I've tracked down the first call to paint which is from fl_unfreeze_form. I have not been able to ascertain what is calling fl_unfreeze_form. Any ideas on how I might? Put that another way. How do I tell gdb to stop execution in fl_unfreeze_form so that I can type 'bt'. Will 'bt' do what I want? Clearly, if we can track down this fl_unfreeze_form (and remove it), then the Xforms frontend will become *at least* twice as responsive as it already is... -- Angus
