Re: [fltk/fltk] fl_choice() doesn't tell you if the dialog was closed (#282)

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.issues  ]
Previous Message ]New Message | Reply ]Next Message ]

Re: [fltk/fltk] fl_choice() doesn't tell you if the dialog was closed (#282) Albrecht Schlosser Oct 18, 2021 top right image

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_ex() or 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.

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.

Direct Link to Message ]
bottom left image   bottom right image
Previous Message ]New Message | Reply ]Next Message ]

Comments are owned by the poster. All other content is copyright 1998-2022 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to ''.