> > Again, what do you mean with "default button"? default button is the button that is presumed clicked when enter button pressed on a dialog, execept if keyboard focus is on a button itself (in which case that button is presumed clicked). This doesn't include checkboxes/radio buttons, just normal buttons. So say I tab to to raido button group, use arrow keys to select, space bar to select, then press enter, the default button should be considered pressed.
> Anyway - if you want to change a widget's features, you are free > to subclass the widget and use the handle() method to make it do > what you want. The core widgets are not intended to do *everything* > that all users expect, but to provide an extendible framework with > features for "standard" applications ready to go. I can do that, can someone provide a simple example. I want to override a Fl_Button to say Fl_Button_X, in the handler I want to say this: if this widget has the keyboard focus and FL_Enter was pressed then do the callback (because this button is considered clicked) (eat the Fl_Enter). I'd also, if not too big a pain, like to override the raido button, and say, if this widget has keyboard focus, select it (this way users don't have to know to press space bar - they can just arrow to select it), then tab is pressed, I want it to go to outside the group the radio button belongs to (instead of tab moving to the next radio button and cause it to be selected). Thanks! _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
