Try using a regular FLTK timer, as you'll have no chance of getting a second process to interact directly with an FLTK app, short of using interprocess control.
FLTK timers don't use threads and should work as you expect, and you are fairly unlimited in what you can do inside the timer callback as far as FLTK is concerned. See Fl::add_timeout() and Fl::repeat_timeout(). There are several examples of using timers here: http://seriss.com/people/erco/fltk/ One of the simplest being: http://seriss.com/people/erco/fltk/#DropShadowBox ringerxyz wrote: > Hi Ian > Thanks very much for your help. > Here is my problem: > In my main app(let's call it mainApp),i need to update a region by timer,but > since this timer is also shared by other funtions,so sometime > the region updated so slowly. > My solution to this problme is to update this region in another process > (i am using embeded linux where there is no pthread), > My code is something like: > > int pid = fork(); > if (pid == 0) > { > //child process > updateregionbyTimer(); > } > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
