This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 23873 - Horizontal arrow keys in the debugger views should move the focus between cells
Summary: Horizontal arrow keys in the debugger views should move the focus between cells
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: akemr
URL:
Keywords: UI
Depends on:
Blocks:
 
Reported: 2002-05-22 22:36 UTC by David-john Burrowes
Modified: 2008-12-22 20:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David-john Burrowes 2002-05-22 22:36:26 UTC
The horizontal arrow keys in the debugger views currently seem to be used to expand and 
collapse nodes in the tree, when there is one.  But, these should actually move the keyboard 
focus between cells in the table.
(we might reasonably use ctrl-left and ctrl-right to expand and collapse tree nodes, though I 
haven't done the research to verify that this is a safe shortcut)
Comment 1 Jan Jancura 2002-05-23 14:37:49 UTC
sorry, 
Comment 2 akemr 2002-05-24 08:50:13 UTC
This is stadard behaviour in JTree, so I don't think
its reasonable to change it.

You can use Tab to move focus between cells.
Comment 3 David-john Burrowes 2002-05-24 17:41:09 UTC
The trouble is that this isn't a tree.  it is a table which happens to have a tree in the first 
column.   
Comment 4 akemr 2002-06-18 08:00:47 UTC
I still don't agree. If you are in first column, you are in tree. Not
easy to implement.
I suggest:
- in first column use horizontal keys to expand and collapse tree
nodes (it's standard)
- use Tabs to move the focus between cells
Reassign to Jano to get his opinion.
Comment 5 David-john Burrowes 2002-06-19 01:17:17 UTC
OK. I talked with some other folks here and here is what I'm thinking 
now:
the notion of using the arrow keys to move the focus around in the 
list is less crucial than being able to expand and collapse the tree 
nodes with the arrow keys (and, as you point out, the tab key does 
move the focus well enough).  So, I agree with you that using the 
arrow keys SHOULD be used to expand and collapse the nodes rather 
than move the focus.

What that means is that this issue should now be phrased as:
The horizontal arrow keys in the debugger views sometimes are used to 
move the keyboard focus between cells.  This should never happen 
anywhere in the list.  instead, when a horizontal arrow key is 
pressed, it should either expand the selected row(s) or it should do 
nothing, because it is undesirable for the arrow keys to move the 
focus around in some parts of the table and not in others.  This 
should also be true for a list where none of the nodes have children.

Comment 6 jrojcek 2002-06-21 15:09:27 UTC
Sounds good. And what about making some modifier (shift?) plus
horizontal arrows move focus horizontally?

Ales may you implement what David John suggested?
Comment 7 akemr 2002-06-25 09:28:48 UTC
OK, fixed in trunk as suggested.

1. Shift+horizontal arrow will move focus between cells,
2. horizontal arrow will expand/collapse in tree column
   and in other columns it will do nothing
Comment 8 David-john Burrowes 2002-06-26 01:08:56 UTC
Argh. :-(  Shift+arrow key shouldn't move the focus, as that is 
usually used to extend a selection.

Can that feature be removed?  (I know you'll say "you should have 
said something about that days ago", and you'd be right.  I did, in 
fact, add a comment about this yesterday, but clearly it didn't get 
into this issue... maybe I wasn't logged on and I didn't notice when 
it reported the error.  Very sorry about this!)
Comment 9 akemr 2002-06-26 11:13:12 UTC
OK, shift+arrow part of fix was removed.
Comment 10 Marian Mirilovic 2002-11-20 10:39:22 UTC
verified in [nb_dev](20021120)
Comment 11 Quality Engineering 2003-07-01 16:26:41 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.