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.
We need better behavior concerning the input verification in NB. I mentioned the New Wizard specifically, but this should be applied to anything that has this same behavior. Currently, if I try to create a new class that has the same name as something else that exists in that folder, the "Finish" button will suddenly disable, without any indication to the user why finish might be disabled. My proposed solution is as follows: 1) Only do verification checking on the input element when user pushes the finish button (can also happen when focus is lost in the input element) 2) Finish button enabled/disabled state should never be affected by verification checking going on in the elements in the pane 3*) If the user pushes the FInish button and there is error on the input, then an error dialog should appear on top of the wizard pane informing user of the error. User should be able to dismiss the error, and work immediately with the wizard pane to correct it and continue with the wizard creation. *May require API changes. See also bug 7367. I filed this bug and the fix does not address the problem well.
reassigned
This won't be fixed in 3.3 bcs it needs wizard redesign. If it blocks other bugs from being solved then change milestone back and increase priority, please.
take a look at the New-->WebServices-->Client wizard in ffj-ee to how it describes for the user why the Next/Finish button is disabled (select a Web Service and invoke the Publish To UDDI wizard -- it uses the same technique).
assing to openide/wizard owner.
It will completely solved during Wizard API redesign (issue 26552). 1+2) is duplicate of issue 7706. 3) is duplicate of issue 28466 (which will be solved in nb35). I close as duplicate of 7706. *** This issue has been marked as a duplicate of 7706 ***
verified