Al wrote: >That's what I wrote about before. You need specialized state variables >to track all changes. This is beyond the scope of a toolkit like FLTK. Many examples (see my previous posts) will not need any state variables
> > Regarding FL_WHEN_CHANGED. I was attempting to mimic the way the mouse > > works, with this button attribute, using short cuts. I thought that the > > intention of FL_WHEN_CHANGED was to allow a user to push and hold a button > > to start an action which then stops when they released the button. This is > > different from a normal or toggle button which would require the > user to push/release a button to initiate an action then push/release > the button to stop the action. > > You can do this. Derive your own class, handle() the push event, Sorry, but now I really have to disagree with this : are you seriously suggesting that as an acceptable workaround for not having good semantics ? I guess what I would like to emphasis here is that we would not need in many situations (many examples have been introduced in this thread) to use inheritance for such a simple thing. What is so hard to accept Al in what was explained ? I don't understand why you're not enthusiastic about finally giving the correct meaning to a so important event that is FL_WHEN_CHANGED, there are almost only advantages to the proposed changes, and simplifications. Frankly, I doubt it would be so hard to achieve and, after all, this is our problem, not fltk users problem. If it is provided that life would be simpler for fltk users and semantics more clear and simple, then it is my belief that we should make it simple even if it's a hell for core developers. > Thanks for your comments. Every comment is appreciated. User comments are vital and should make us reconsider our positions. As I said to the cairo project boss with humor recently (and he agreed) is: Open Source rimes for me with Open Minded. Fabien _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
