> Fabien Costantini wrote: > >> What is the normal use of a FL_NORMAL_BUTTON from a user's view? > > But here's where my opinion still _really_ differs from yours: > > IMHO, it is really important to handle both events (key push and released) > > exactly as for the mouse when user specify to use FL_WHEN_CHANGED option. > > I won't insist on my opinion, but I still think that this could also be a > case for subclassing. We don't need to support all odd button features Not all but this one is important semantically speaking, and is not so hard to achieve if we code it properly once for all. The problem is - and I won't particularly criticize the existing code as we all do that and I feel as guilty as others - that we add something on something all the time without taking enough distance and thus accumulating bugs and complexity. I'm sure the most important thing here is to specify precisely what to do (I started to do that by writing a mini spec. in my previous posts that our discussion is completing). Once we are all clear on the specs, it will be quite easy and I can handle that (with your help to raise possible bugs in first versions :-) This makes me think of a new branch especially for that one if all are OK. > Well, that doesn't count. ;-) If we need it, we can extend the menu or > change it to an array of toggle buttons for each bit, can't we? Again it's a matter of semantic, a change is a change and fl_release is indeed a change. Al, I think you start to know me and you noticed how easy going I can be concerning modifications, if it pleases other team developers.
Today, I will insist on that one that shocks me particularly in the toolkit and hope that everyone in the team takes 10 minutes to think about it, because to me ; it's simply not coherent. Fabien _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
