You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sergey Derugo (JIRA)" <ji...@apache.org> on 2008/11/05 15:07:44 UTC

[jira] Closed: (WICKET-1619) PagingNavigator.setEnabled(false) doesn't work

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

Sergey Derugo closed WICKET-1619.
---------------------------------


> PagingNavigator.setEnabled(false) doesn't work 
> -----------------------------------------------
>
>                 Key: WICKET-1619
>                 URL: https://issues.apache.org/jira/browse/WICKET-1619
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.3
>            Reporter: Sergey Derugo
>            Assignee: Igor Vaynberg
>             Fix For: 1.3.6, 1.4-RC2
>
>         Attachments: 1619.patch
>
>
> 1. Create paging navigator PagingNavigator 
> 2. call PagingNavigator.setEnabled(false)
> 3. navigator will be rendered as enabled, if click on any link ("1", "2" etc) - content of the data view will be changed.
> In many cases it's necessary disable navigator, for example, when user need to edit only single line of DataView other controls need to be disabled. 

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