DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2166 Version: 1.3-current I've just had a quick look at this. While not immediately intuitive, I think that this is a deliberate feature. The reason I say that is that once the user tabs into the Comments field, it is not possible to tab out again because the tab is added to the Comments field. Similar behaviour can be seen in the main Widget Properties dialog, If the user clicks on a field, eg Class field on the C++ tab, and then hits the tab key to move on, s/he will eventually get stuck in the Callback field and be unable to tab out of it. To get round this it looks like there has been a deliberate decision that the default tab navigation only cycles between the "Live Mode", "Hide Overlays" and "Close" buttons at the bottom. IMHO, the "fix" here is to restrict the default tab navigation to cycle between just the "OK" and "Cancel" buttons. If the user then selects another field, all bets are off because the tab might get eaten by one of the fields in the non-default tab navigation order. (That's a clumsy sentence, but I hope it makes sense) I suggest we bump this STR up to 1.4 for the moment because: (a) it's not critical for the release of 1.3; and (b) to verify/discuss/correct the tab navigation order in all of the dialogs in fluid could take some time Link: http://www.fltk.org/str.php?L2166 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
