United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6355949 jconsole: Tab and Enter keys are not working correctly in the Connection dialog
JDK-6355949 : jconsole: Tab and Enter keys are not working correctly in the Connection dialog

Details
Type:
Bug
Submit Date:
2005-11-28
Status:
Closed
Updated Date:
2011-03-08
Project Name:
JDK
Resolved Date:
2011-03-08
Component:
tools
OS:
generic
Sub-Component:
jconsole
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:

Related Reports
Backport:

Sub Tasks

Description
Two problems with the Connection dialog:

1. Once you have moved the focus to the local process list when you are pressing Tab key the focus moves on every second key press and doesn't leave the local processes list

2. Open Connection dialog, select a process in the local processes list, then click on 'Cancel'. Press Ctrl+N: the connect dialog appears again. Press Tab or Enter key, either one doesn't work, although the 'Local Process' radio button is active and there is a selected item in the local processes list.

                                    

Comments
SUGGESTED FIX

1. Make tab key jumping to the next entry in the local processes list on every keypress and jumping to the 'remote process' radio button from the last entry in the list.

2. Make Tab and Enter keys working
                                     
2005-11-28
EVALUATION

I can reproduce the problems.  For #2, when I click on the local processes table (make the table active), the key works again.
                                     
2005-11-29
EVALUATION

About #2: exactly, if you open the dialog again and don't click on the local process table (they are selected anyway), Tab and Enter will not work. When you click on the table, they start working.
                                     
2005-12-02
EVALUATION

#1 is due to Swing's focus management design. You need to type ctrl-Tab to move focus from a table to the next component.

#2 is a bug and should be fixed. It happens often when jconsole is started with no arguments and there are no other java processes running. The local table shows one
line selected, but the Connect button is incorrectly disabled.
                                     
2006-10-20



Hardware and Software, Engineered to Work Together