Re: RefreshingView only gets rendered when TreeTable node is opened twice
file a jira issue and attached a quickstart: https://issues.apache.org/jira/browse/WICKET-892 On 8/27/07, Gerolf Seitz [EMAIL PROTECTED] wrote: i'm using trunk (as of yesterday) 1.3.0-SNAPSHOT i'll file a jira issue later today, including a quickstart gerolf On 8/27/07, Matej Knopp [EMAIL PROTECTED] wrote: It's probably a bug, can you please fill in a JIRA entry and assign it to me? What wicket version are you using? -Matej On 8/27/07, Gerolf Seitz [EMAIL PROTECTED] wrote: hi, i have a refreshingview in a treetable column, but it only gets rendered after opening, closing and again opening the corresponding treenode. did anyone else notice this misbehavior? thanks for any hints, gerolf
Re: RefreshingView only gets rendered when TreeTable node is opened twice
fixed On 8/27/07, Gerolf Seitz [EMAIL PROTECTED] wrote: file a jira issue and attached a quickstart: https://issues.apache.org/jira/browse/WICKET-892 On 8/27/07, Gerolf Seitz [EMAIL PROTECTED] wrote: i'm using trunk (as of yesterday) 1.3.0-SNAPSHOT i'll file a jira issue later today, including a quickstart gerolf On 8/27/07, Matej Knopp [EMAIL PROTECTED] wrote: It's probably a bug, can you please fill in a JIRA entry and assign it to me? What wicket version are you using? -Matej On 8/27/07, Gerolf Seitz [EMAIL PROTECTED] wrote: hi, i have a refreshingview in a treetable column, but it only gets rendered after opening, closing and again opening the corresponding treenode. did anyone else notice this misbehavior? thanks for any hints, gerolf
Re: RefreshingView only gets rendered when TreeTable node is opened twice
i'm using trunk (as of yesterday) 1.3.0-SNAPSHOT i'll file a jira issue later today, including a quickstart gerolf On 8/27/07, Matej Knopp [EMAIL PROTECTED] wrote: It's probably a bug, can you please fill in a JIRA entry and assign it to me? What wicket version are you using? -Matej On 8/27/07, Gerolf Seitz [EMAIL PROTECTED] wrote: hi, i have a refreshingview in a treetable column, but it only gets rendered after opening, closing and again opening the corresponding treenode. did anyone else notice this misbehavior? thanks for any hints, gerolf