[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L1691
Version: 1.3.0
Fix Version: 1.3.0 (r8035)
Fixed in Subversion repository.
This is now a user setting in FLTK 1.3. The NORMAL_INPUT_MOVE macro is now
used as a shortcut for this user setting:
Fl::option(Fl::OPTION_ARROW_FOCUS).
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L1691
Version: 1.4-feature
Link: http://www.fltk.org/str.php?L1691
Version: 1.4-feature
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L1691
Version: 1.3-feature
Link: http://www.fltk.org/str.php?L1691
Version: 1.3-feature
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L1691
Version: 1.2-feature
Bumped to 1.2, where we might make this a user setting.
Link: http://www.fltk.org/str.php?L1691
Version: 1.2-feature
_
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Oops.. I got my STR's mixed up. Please ignore previous text.
As for this one, I guess it's a feature request, not a bug.
Link: http://www.fltk.org/str.php?L1691
Version: 1.1-current
__
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Surely it's a public API -- see Fl_Widget.H, and the documentation.
Personally, I discovered it by trying to use the API as it's described
(checking a bunch of widgets in response to an OK button). Maybe
I'
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Is this really a bug though?
It doesn't refer to any public API of the library, rather to a code hack
that's been there (and I suspect never really used) for so long... I doubt
the average user would ever enc
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
In Fl_Input.cxx we find:
// 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 i