But it is also a bug in the TabbedPanel which should work well without tabs.
Christian Helmbold-2 wrote:
What if you use two different tabbed panels on the same page?
Good point! It doesn't work with two panels on the same page! I don't
know why
and how to fix it.
It was a
The development of the bookmarkable tabbed panel component is continued on
http://wicketskunkworks.org. We decided to use a Google Code project for now
but we plan to make the final component available via wicket stuff or maybe in
the extensions tree of the core distribution (i don't know if
What if you use two different tabbed panels on the same page?
Good point! It doesn't work with two panels on the same page! I don't know
why
and how to fix it.
It was a mistake in my test code, that lead to this error. I accidentally added
the tabs of my second tabbed panel to the
Instead of competing, why don't we set up a project some place and check both
solutions in under different packages?
We can then refactor them into one and take the best of both :)
I agree. Is there an existing place in the wicket project to do this?
I've discovered some troubles in my
In my code were two little bugs. If the constructor with parameter
defaultTabIndex was used, the active tab was always set to this value
regardless what tab the use clicked on. The other issue affected the specified
parameter name that stores the active tab. It did not work in the constructor
Yes, because you no longer have the previous state... I have the same
problem, but maybe some ideas for a solution.
- Brill
On 10-Mar-09, at 11:25 AM, Christian Helmbold wrote:
Instead of competing, why don't we set up a project some place and
check both
solutions in under different
