> I would still like to load the dll at some time shortly after startup, > just to prevent later errors, if someone would start watching sockets > with add_fd() at a later time, and the winsock dll can't be loaded then. Interesting: We could satisfy both developers kind (those using wsck and not using it) by making visible/callable to you a static fl_winsock_preload() api this would make you controlling exactly where and when you 'd like this lib to open in your 3rd party app, while not loading unnecessarily the lib for others ? Thanks, for the debug report I'll change it to Fl::error() so that it can be seen by non console supported fltk apps too.
Fabien _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
