> > I am not opposed to the worker thread not calling the > redraw method. Though I guess I'm at a loss for how I could > force it to call after updating the pixel buffer without > making a call to it from the worker thread. > > Well, I think you're okay with calling redraw from the worker thread. > > Ian wrote earlier in this thread: > > > Do not call redraw(); at all from the helper thread, as it won't > > do what you want... > > I don't know what Ian thought what you would want, but if > you know that redraw() doesn't draw immediately, but instead > marks the widget to be redrawn later, and if you wake the > FLTK main thread with Fl::awake() after redraw(), then I think > that that should work as expected. > > Ian, any comments ?
I don't know what I meant either. I've just spent a little time looking at the code for redraw(), and I can't see any real reason why it would not be safe to call it from the worker thread, if you've got the lock first... Yet I know I have a worry in the back of my head that there's something hooky with this... If it actually works, I guess that's a good starting place! -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
