Regarding my core working algorithm: This is CPU intensive, depending on the user settings it can completely hang the program.
Even with settings that generate results faster it can still potentially be slow to complete a single cycle. but regardless of the above, even using fast parameters i need to allow the user the option of halting it, viewing results or whatever, then restarting if required. Sooo, my event needs to register also within the algorithm. Given what i've read today and how it differs from my traditional idea of event handling, i think this be accomplished just with the native event structures as descirbed and a single thread. but, given this CPU usage issue (i may block or warn users at certain settings) then would a second thread be the best option? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
