On 23.09.2010, at 14:11, MacArthur, Ian (SELEX GALILEO, UK) wrote: > >> I'll just remove the OleInitialize call in the >> Fl_Win32_At_Exit destructor to patch the FLTK library that >> comes with Csound. I'd much rather have the ref count >> unbalanced in the positive direction instead of the way it is now. >> >> Would a configure flag like "--disable-oleunitialize" be >> considered for the FLTK build on Windows? > > Hmm, I doubt it, I think we'd rather have an actual fix.
And so do I. > It sounds, from what Albecht says, as if we should be dong this right > anyway but that maybe our internal refcount is not being updated > everywhere it ought to be... I only took a short look at it (a little grep and such), but it seemed so. I'm thinking of making a single function, say fl_OleInitialize(), that keeps track if it has been called already (instead of the different places in the rest of the code), and then the destructor could just ask the flag if it should do the OleUninitialize call. Or so... Some of the different calls seem to be due to the (previous external) Fl_Native_File_Chooser that might have missed the integration with this MS-specific Initialize and Uninitialize (what a word! ;-) stuff. > Or maybe I just misunderstood. > > Probably a good idea to post an STR resording your findings though, so > that we have a record to remind us! Yes, I think it's time now. Andy, would you please do it? Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
