> > On 6 Nov 2011, at 06:13, David wrote: > > > Okay, well, tonight I decided to check for timer functions and found = > them and came up with the following. The only quesiton I have is if the = > Stop() routine loop of 4 checks is okay or if slow X server/client = > communcations would matter? Wouldn't it all just be sent down? maybe = > use Fl::flush instead? > > David, > > I confess I'm struggling to grasp what it is you are actually doing, so = > I'm certainly missing the point of your code. > > However, I have to say that all looks very platform-specific, so I'd = > have to think that the just has to be a better way! > > A pop up window that says "Please Wait..." within the same thread. I got it working now with my keepalive class and the adjustments made to it (plus as mentioned, the paint after removal is optionally since it goes back tot he main fltk loop after the window goes away).
However, I did also mention that maybe using XInitThreads and XLockDisplay and XUnlockDisplay would allow FLTK to support opening windows in multiple threads????? maybe someday I can lean more about X and look at making it able to open multiple windows in different threads, but I got FLTK about where it is needed for me to complete the linux app. I'd like to see those improvements implemented before too many changes occur, especially the one that just moves data that was all in a .H file to two files .cxx and .H. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
