> > There will probably be several responses, ... I hope so :)
> > > I'd like to have keyboard navigation enabled inside the popup. > > That should be automatic; FLTK already does keyboard nav > for normal widgets that expect input (Fl_Input, Fl_Button, etc). > So if all the days in your calendar are an Fl_Group of > Fl_Buttons, > that should work automatically. Sort of. If the calendar is a (normal) subwindow, the automatic navigation leads off the end of the calendar back onto the main window. At least I think it does. > > > And, as the subject line suggests, what's the preferred > > way of communicating a result back to the main window > > There are many ways to do it, but the 'cleanest' is to follow > the same techniques FLTK itself uses; use a callback() i > the user hits the 'OK' button. eg: > > [..] > depart_calendar = new MyCalendar(..); > depart_calendar->callback(DepartCalendarOK_CB, (void*)this); > [..] > > ..and the DepartCalendarOK_CB() function expects a pointer to the > calendar widget, ... It's not clear to me where the new MyCalendar would get deleted in that scenario. > > and dismissing the child? > > Just hide() the widget. > > Either have it be automatic when the user hits OK or Cancel, > or have it be something your 'OK Callback' has to call .. Yes, that makes sense if there's just one. Maybe I'm stuck with that. Thanks for the ideas! _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
