You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2007/09/01 01:05:18 UTC

[jira] Assigned: (WICKET-915) Next button not being enabled/disabled in Wizard when programitically calling setEnabled

     [ https://issues.apache.org/jira/browse/WICKET-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg reassigned WICKET-915:
------------------------------------

    Assignee: Eelco Hillenius

> Next button not being enabled/disabled in Wizard when programitically calling setEnabled
> ----------------------------------------------------------------------------------------
>
>                 Key: WICKET-915
>                 URL: https://issues.apache.org/jira/browse/WICKET-915
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.3.0-beta2
>            Reporter: Doug Leeper
>            Assignee: Eelco Hillenius
>         Attachments: wicketTest-src.jar
>
>
> When I create a WizardStep, I automatically call setComplete( false ).
> When the user performs the necessary option (selects an item), I call setComplete( true ).
> However, the Next button is disabled even though I called setComplete( true ).
> Actually, I found out that once you call setComplete( false ) or if isComplete() returns false, the Next button will never become disabled. 
> Note: this behavior only is exhibited in the attached example.  A pared down example (not attached) preforms as expected, i.e. a button has a link that toggles complete for the step

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.