FLTK logo

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 19, 2021  
 

1.4 would be for ABI breaks only, AFAIK.

As Greg said. API breaks are bad because they would break existing user programs. We try to avoid that in all 1.x versions, unless ... (see Greg's comment). Adding new functions is always possible, this would neither break the API nor the ABI.

Deprecated functions and methods may be removed in later versions which would break the API - but that's something that needs to be done at some time. For instance: deprecated in 1.3: remove in 1.5 or later. But we're very conservative WRT removal of deprecated functions.


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 ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

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