Albrecht Schlosser schrieb: > in general, we *can* now add ABI-breaking features if we're convinced > that they will/should be in a future version of FLTK and that they are > not too big a change so that we can maintain the code with all the > necessary #ifdef's.
In general it is possible, but you need to be convinced of it. So to me the best way to proceed seems to be, that I realise my detailed concept and come back, when it works for all examples. Then you can decide about "too big a change". But before that, there is a basic question - do you in general think, it should be implemented? You told me, that would break your own system of realising that. Mine too, but to me it is not a problem to delete something and replace it by "built in solution". The point is, that the changes should be compatible to existing solutions. Does "being convinced" just depend on code, or are you not convinced at all, that the effort makes sense? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
