On 31 Jul 2007, at 17:38, Cavit Cahit VURAL wrote: >> >> I think we need a bit more detail; what happens to cause the input >> widget to lose the focus in the first place? > > User clicks another Input on window or presses the Tab key or .... > The cause is not important
Well, with respect, I think knowing *why* the input widget lost the focus in the first place is absolutely the crux of the problem. You say the focus is lost because the user chose to click on another input, yet you do not want to allow the focus to move to the widget the user has selected? That sounds like seriously bad UI design - why would you want to do that? If the user *must* enter valid data into an input field before being allowed to proceed, then would it not be better to have the widgets callback fire when the user leaves the widget? In the callback, you can scan whether the input is valid, and if it is not you could either pop a dialog box warning of the invalid input, or at that point, from the callback, throw the focus back to the invalid input widget - rather than trying to throw it back from the handle method... Any good? But I do not know exactly what you are trying to do, so I may be missing the point. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
