> This is "normal" GUI behavior. Please look at your constructor again. There is > no drawing. All drawing happens in your draw() method. But the draw() method > will not be called by show(). This is delayed until FLTK decides that there is > nothing else to do, and there are no more window messages (mouse movement, > keyboard events and so on). Then FLTK will eventually call your draw() method, > and your image will be rendered on the screen.
Extremely well put, Albrecht. I was expecting invoking "show() _WOULD_ immediately (well with a bit of massaging) invoke draw(). That FLTK would "loiter in the background until it was good and ready to draw()" was NOT what I was expecting at all. To be clear, I _did_ attempt all manner of "triggers/flushes/bludgeoning" to make the image render on command, including multiple invocations of Fl::check(), Fl::flush(), etc. From Ian's posting, I now understand that flogging my end of the "pipeline to X" won't make the handshaking move any faster. If I have to yield a bit of time to fltk for 'background processing' like responding the X messages to get the image displayed, then so be it. <snip> >...(extensive, meaty explanation)... >...(extensive analysis & commentary)... >...(simple illustrative program)... </snip> I don't know what to say - Outstanding, Albrecht! I really appreciate the extensive effort you've put into explaining & illustrating in a clear & concise manner, the details of the processes involved. I hope this thread will be as educational for inquiring minds for years to come as it has been for me. I thank you, Albrecht, Ian, Mathias and everyone else who replied for your patience & support. Regards, Robb. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
