I suspect there are some implications. Any comments? On Wed, May 25, 2011 at 11:47 AM, asif saeed <[email protected]> wrote:
> But I am linking to FLTKDLL - that is, dynamically. Are there any > implications? > > > On Wed, May 25, 2011 at 10:49 AM, asif saeed <[email protected]> wrote: > >> I guess there will be no problems as SL is calling my supplied >> object/function in a separate thread (as somebody has just told me). >> >> >> On Wed, May 25, 2011 at 10:45 AM, asif saeed <[email protected]> wrote: >> >>> Hi, >>> >>> In my current application, I have a .cpp file with #includes of MFC >>> headers and headers of a static lib built upon MFC. The static lib (SL) >>> register function takes a void* (this pointer) of an object and an address >>> of a static function - this registers a callback with SL. From inside that >>> static function, you're supposed to static_cast void* to your own object and >>> call a method of your own object. Now this callback can trigger at any time. >>> The frequency of callback is not that high and it is a single-threaded app. >>> I am basically converting an MFC application to FLTK. I wonder if, after I >>> show an FLTK GUI window, such as that of a hello world type, the callback >>> function of my object in my FLTK app will still get called. I think this can >>> be done as I am linking to a static MFC library (SL). There are no MFC vs >>> FLTK problems, I have isolated both of them. I need your feedback. >>> >>> Thanks & regards,Asif >>> >>> >> > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
