Hi Lucy, we're using GitHub issues only for error reports and feature requests.

A short answer is that you don't need to return immediately after Fl::run() and that you don't need to care about memory leaks if you return after some time and don't work with FLTK in a continuous loop, i.e. opening and closing different windows with their widgets. User support is available in our Google group and/or mailing list. If you need more help, please see the information below. Thank you.

This is the wrong place to ask questions about building or running programs with FLTK (user support). FLTK "issues" are reserved for bug reports and requests for enhancements, for further information please visit https://www.fltk.org/bugs.php.

Please ask user questions in our user group fltk.general. Your question will have a wider audience and you will likely get more and quicker replies.

Please include the system/platform (Windows, Linux, macOS), the build system (Visual Studio, CMake, Ninja), compiler (gcc, clang), compiler version, and build error messages in text form (copy and paste preferred). TIA.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.