> > So could be something with mixing Fl_clock with "Printer > dialog", maybe > > Fl_Clock starts any thread ??? or it's casuality and the problem is > > memory overwite.
Hmm - interesting idea. If it is a memory problem, can you run it under the MS debugger? Does it catch memory access errors? > Without commenting Fl_Clock when the "Printer Dialog" is > shown the clock > stops ticking, probably "Printer Dailog" as modal window absorb all > events and maybe meanwhile "Fl::add_timeout(1.0, tick, v)" are > accumulated (less probable) or not removed. It is normal on win32 for the window to not refresh whilst it is being dragged, or has a modal window on top of it. I don't *think* that can be the cause... I see the same behaviour here but do not get the zombie... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
