> The "thread" write his progress in > global > structure variables (volume, duration) and "timeout" read these > values and refresh the popup window (every 0.1 sec). Now "thread" do > nothing with GUI, only "timeout" interact with it between "lock" and > "unlock" call.
One further thing to note: If the F::add_timeout() call is made to create the timer from the main() thread (and it ought to be) then it will operate as a part of the main() thread, and therefore the lock/unlock will not be necessary, since the main thread manages it's access to the GUI automatically for you. Only worker threads need to lock/unlock around access to the GUI (since they can not know the state of the main thread and whether it is actively updating the GUI when they run.) Other than that, it all sounds like you have it working now, which is good. 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
