A little clunky, but acceptable if that's the best way to avoid ABI/API changes. :)
@CendioOssman Thanks for your comment. My current implementation for 1.4.0 avoids this extra call by adding a new function as I mentioned above. I'm not yet clear about the name though.
fl_choice2() would be one option,
fl_choice_ext() are other options. I'm (still) open for suggestions.
Due to the massive changes in the implementation caused by STR 3242 it's very unlikely that this will ever be available in 1.3 though (we don't add new features anymore).
I can't think of a use case for that off hand, no.
The new function will return
-1 for window close, no matter if the
Escape key was hit or the window close button was pushed.
Your function name choice or "better" proposals would be appreciated.
[ Direct Link to Message ]
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.