constructor cant since at that point you havent been added to the form yet.
but onbeforerender() can.
onbeforerender() { if (findParent(Form.class)==null) { throw }
super.onbeforerender(); }
-igor
On 8/16/07, Tauren Mills <[EMAIL PROTECTED]> wrote:
>
> Sure, that makes sense. So to clarify
Sure, that makes sense. So to clarify, it is up to the user to
include a form around the datatable if they want to include a
filtertoolbar?
To test for this requirement, would the constructor of filtertoolbar
check to see if one of its parents is a Form? Or a
IFormSubmitListener? I can write so
i guess what needs to be done is that FilterForm should go away, whatever it
does now should be moved into filtertoolbar. then a requirement to adding
filtertoolbar to the table is that that table itself is wrapped in a form.
makes sense?
-igor
On 8/16/07, Tauren Mills <[EMAIL PROTECTED]> wrote:
Igor,
How would you suggest doing this refactor? The form really should go
outside of the table, but that puts it outside the realm of
DefatultDataTable since the wicket:id for it is on a tag. If
DefaultDataTable does add the form somehow, what about when you don't
want filtering? Then the tab
yes, i believe it is caused by invalid markup, maybe the form should be
factored out and put around the entire table.
-igor
On 8/14/07, Tauren Mills <[EMAIL PROTECTED]> wrote:
>
> For some reason when I do an ajax refresh of the DefaultDataTable in
> wicket-phonebook, the FilterToolbar disappear
For some reason when I do an ajax refresh of the DefaultDataTable in
wicket-phonebook, the FilterToolbar disappears. I see it in the Ajax
Debugger, but it doesn't display on the screen. This is only
happening in FF, not IE (only tested on WinXP).
I cannot see any difference between the html that
