> Following this discussion I experimented a little and made a test program for > a splash screen without messing around with timers and signals. I started > with the threads example in the test folder. Due the implementation of > threads.cxx this code snipped only works in the test folder because it uses > threads.h and config.h. > > The program creates two successive splash screens after startup while > performing (or simulating to perform) some time consuming operations. > Afterwards it displays the main app screen. > > I tested it only on Linux. > thanks - however they were saying it should be done only in the main thread (that's why signaling was used). One thing is the first lock call should be in the main thread since it does some initialization, not sure if that would then cause a problem, but if it works, that would have been better (but still would have that window closed clean up issue until the main loop started).
_______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
