Re: [Wicket-user] Schizophrenic Components (that suddenly change their Variation)

2006-08-02 Thread Igor Vaynberg
either switch panels or add both and override isvisible() on each one-IgorOn 8/2/06, Eelco Hillenius < [EMAIL PROTECTED]> wrote:I haven't read it in detail, but variation is not meant for doing that kind of stuff (though it should work). Rather, use panels andreplacement (switch the panels).EelcoOn

Re: [Wicket-user] Schizophrenic Components (that suddenly change their Variation)

2006-08-02 Thread Eelco Hillenius
I haven't read it in detail, but variation is not meant for doing that kind of stuff (though it should work). Rather, use panels and replacement (switch the panels). Eelco On 8/2/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > I guess it is because Wicket caches the Markup associated with a

Re: [Wicket-user] Schizophrenic Components (that suddenly change their Variation)

2006-08-02 Thread Juergen Donnerstag
I guess it is because Wicket caches the Markup associated with a Component. Wicket assumes that the associated Markup does not change once loaded, except if you change the markup file content itself, because the cache will be cleared than. I guess I would create two separate Panels for LoggedIn and

[Wicket-user] Schizophrenic Components (that suddenly change their Variation)

2006-08-02 Thread Stefan Arentz
I have a simple Panel that we call the QuickLogInPanel. This is a panel located in a 'side bar'. When the user is not logged in the panel shows a simple username/password form. After logging in I want to show just some text and a log out button. So I did this: public class QuickLogInPanel extends