[jira] Resolved: (WICKET-1441) TabbedPanel does not refresh unless you call setSelectedTab

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

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

Igor Vaynberg resolved WICKET-1441.
-----------------------------------

       Resolution: Won't Fix
    Fix Version/s: 1.3.3
         Assignee: Igor Vaynberg

there is no way for us to know that you have changed the list unless we do something like proxy it which i am not a fan of. furthermore, lets say we do proxy it and you call the set on the index that is the current - does that mean you want to replace the currently selected tab right away? or maybe you want to wait for something else.

furthermore what if you have a tab impl that can take a panel, so instead of calling a set on the list you do get(current).setpanel(panel) then there is still no way for us to do it automatically.

so i think what you do right now works, we might add a refresh() method that would do that, but i dont know if that is necessary...

> TabbedPanel does not refresh unless you call setSelectedTab
> -----------------------------------------------------------
>
>                 Key: WICKET-1441
>                 URL: https://issues.apache.org/jira/browse/WICKET-1441
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.2
>            Reporter: Erik van Oosten
>            Assignee: Igor Vaynberg
>             Fix For: 1.3.3
>
>
> When you replace the currently selected tab (e.g. something like tabbedPanel.getTabs().set(0, new ...)), the tabbed panel is not refreshed. (Observed with code in the onsubmit of a form.)
> Workaround: call setSelectedTab(getSelectedTab()) on the tabbed panel.

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