matthiasm wrote: > > On Aug 27, 2007, at 8:35 AM, Manoj wrote: ... >> 2. If i have some controls (FL_Input, FL_Output etc) and when i move >> the left or right arraw key( -> or <- ) then cursor goes to each >> control. It's not fit inside one control. I mean if i'm moving the >> cursor by arrow in FL_Input control then it should not go out of this. > > There is some setting that you change at compile time of FLTK if you > don't like this. I can't remember what it is though. Anyone?
src/Fl_Input.cxx, line #64 ff. (FLTK 1.1.8/svn r5837): // If you define this symbol as zero you will get the peculiar fltk // behavior where moving off the end of an input field will move the // cursor into the next field: // define it as 1 to prevent cursor movement from going to next field: #define NORMAL_INPUT_MOVE 0 Another way to achieve this (without modifying FLTK sources) would be to derive your own widget(s) from Fl_Input and modify handle() to catch these keys when the cursor is at the beginning or end of the input, resp.. That's what I did, when I decided, not to modify the FLTK sources any more. >> 4. If i create a modeless dialog then i dont find system >> menu(minimum,maximum and cross) on this dialog when it displays. > > You can create normal windows, non-modal windows, and modal windows. > Depending on the operating system that you run, FLTK will show or not > show the system window icons. Normal windows always have them (unless > they are borderless), and modal windows never have them. With non-modals > (usually floating toolboxes) it depends on you OS. You can, however, double click in the windows headline to maximize the modal window (at least, if there is a resizable() in it, but I'm not sure about that). Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
