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 10558 - Return doesn't activate Next button in wizard with instructions on first page
Summary: Return doesn't activate Next button in wizard with instructions on first page
Status: CLOSED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: UI (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P3 blocker (vote)
Assignee: Vladimir Zboril
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-03-22 00:56 UTC by Rochelle Raccah
Modified: 2005-03-09 04:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rochelle Raccah 2001-03-22 00:56:32 UTC 
If the first page of the wizard contains instructions which don't accept focus,
the next button doesn't work by hitting return unless you click it, then click
Back.

Look at the RMI wizard for an example of this behavior.  It is broken on Windows
NT and 2000, but works on Solaris.
Comment 1 jrojcek 2001-03-22 13:37:08 UTC 
Actually problem is that text area in this wizard (and maybe also in others)
accepts focus, it is only not eidtable. So it should be used setEnabled(false)
for components which should not accept focus.
Same problem is in New module wizard.
Comment 2 Rostislav Levy 2001-03-22 17:37:46 UTC 
Repair New Module Wizard.
Comment 3 Rochelle Raccah 2001-03-22 18:06:44 UTC 
The reason setEditable is false in our case but setEnabled is true is so the
user can highlight the text and copy it somewhere.  I don't think we want to
lose that functionality, but I'm in the middle of checking for sure with HIE.

Also, we can't get the text area to take focus at all, and it works on Solaris,
so is there some other solution we can find?
Comment 4 jrojcek 2001-03-23 11:40:33 UTC 
It works on Solaris and Linux but if you try tab key then you can set focus to
text area and you will not be able to use enter for default button invocation. I
think from this point of view this is not a bug. Or it is bug in swing that text
area consumes Enter and Tab key events also if it is in non editable state. 

Other thing is that it works different on Solaris and Windows.
Maybe user should know that Ctrl+Enter always invokes default button.
Comment 5 Vladimir Zboril 2001-03-25 14:34:42 UTC 
Fixed in main trung and release32 too.
Comment 6 Jan Chalupa 2001-05-06 15:12:12 UTC 
Target milestone -> 3.2
Comment 7 Quality Engineering 2003-07-01 15:16:10 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 8 Quality Engineering 2003-07-01 15:19:26 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.