| | [ Return to Bugs & Features | Roadmap 1.3 | SVN ⇄ GIT ]
STR #2166
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 3 - Moderate, e.g. unable to compile the software |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | FLUID |
|---|
| Summary: | New fluid "Comments" field: bad tab navigation order |
|---|
| Version: | 1.3.3 |
|---|
| Created By: | greg.ercolano |
|---|
| Assigned To: | matt |
|---|
| Fix Version: | 1.3.4 (SVN: v10658) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | greg.ercolano
05:09 Mar 03, 2009 |
| When using <tab> key navigation to move through fields
in the fluid dialogs, the new 'Comments' field that's been
added needs to have its tab order fixed..
Hitting <Tab> on the field *above* the new Comment: field
should move focus the comment field, but the order is wrong,
focus moves to the OK and Cancel buttons instead.
Noticed this in at least two dialogs:
1) "Declaration Properties"
2) "Function/Method Properties"
Should be easy to fix. | |
| |
| #2 | engelsman
13:53 Mar 27, 2009 |
| 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 | |
| |
| #3 | greg.ercolano
15:31 Mar 27, 2009 |
| Feel free to bump to 1.4, not critical. | |
| |
| #4 | matt
07:12 Apr 02, 2015 |
| Fixed the Tab order in Fluid dialogs that contain a comment field. The comment field can no longer have tabs in it anymore (hey, it's either that or the other, right?). But I believe that this is a limitation that the user can easily live with. It's just comments, not code.
Please let me know if I missed a Comment field. | |
[ Return to Bugs & Features ]
|
| |
