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.
Summary: | [2004-03-31] Need to be able to dynamically enable/disable Finish button | ||
---|---|---|---|
Product: | platform | Reporter: | Unknown <non_migrated_user> |
Component: | Dialogs&Wizards | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | benway, dstrupl, eakle, jglick, jrechtacek, mentlicher |
Priority: | P3 | Keywords: | API, API_REVIEW_FAST |
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 26552 | ||
Bug Blocks: | 15267, 21669, 22145, 37398 | ||
Attachments: | patch for review |
Description
Unknown
2000-09-18 21:55:31 UTC
Automated change of version from Other to Dev. You can have JPanel behave like WizardDescriptor.FinishPanel and like WizardDescriptor.Panel simply by creating two different implementations of WizardDescriptor.Panel delegating to the same JPanel. I mean the JPanel not to implement the interfaces but rather create separate objects. And the iterator can decide whether the next step will be FinishPanel or not. I am marking the bug as invalid - if you don't agree please comment and reopen (if you reopen the issue please use type enhancement instead of deffect). I see in the comment that it is possible to do this. However, it should not be that hard to do and it should not require research to figure out. This is something that people developing wizards need to do quite often. The feature requested here (I am reopening and changing to ENHANCEMENT) should be a basic, documented Netbeans wizard feature supported in the API -- the ability to enable and disable the Next and Finish buttons independently. See also related issues 15267, 11694 and 23116. issue officially requested by S1S, planned for 4.0, prio P1 These issues have been reported to be part of Sun's "should have" contribution to NetBeans 4.0 and be "high level" issues. That is why I am changing them to be FEATUREs with P2. If you think I've done wrong change, please update the issue and internal documents. API ease-of-use issue. I am lowering priority because there is a straightforward workaround as David described. Should be better documented or a more obvious API provided, e.g. public interface FinishablePanel extends Panel { boolean isFinishPanel(); } (marking FinishPanel @deprecated) *** Issue 14317 has been marked as a duplicate of this issue. *** *** Issue 22145 has been marked as a duplicate of this issue. *** *** Issue 15267 has been marked as a duplicate of this issue. *** No changes planned to 3.6. draft implementation was commited in wizards_36584 branch (use cvs update -f -r wizarrd_36584 openide/src core/windows/src) Created attachment 14083 [details]
patch for review
Dear reviewers, please could you review the attached patch before merge to maintrunk? Thanks Thanks for review, the proposed change intergrated in maintrunk. This issue was solved long time ago. Because nobody has reopened it neither added comments, we are verifying/closing it now. If you are still able to reproduce the problem, please reopen. Thanks in advance. |