that doesn't matter, We don't store them (the changes for rollback) anymore but the page still gets the events. Because we still have to know it so that we can increment the page counter...
johan On 9/27/07, Sam Hough <[EMAIL PROTECTED]> wrote: > > > This posting put me off using the change recorder: > > http://www.nabble.com/forum/ViewPost.jtp?post=12473029&framed=y > > Did I get the wrong end of the stick? > > > > Johan Compagner wrote: > > > > we already have a change recorder on a page for its components, all > > the methods you mention should also call that.
Then it can also be > > made much more fail prove because a component should just 'fire' call > > the change method. because state is not just those what you mention > > but could be anything > > > > On 9/26/07, Sam Hough <[EMAIL PROTECTED]> wrote: > >> > >> Eelco, > >> > >> Meant to say we have our first case where we want a component to update > >> because the model has changed. It is a field that only gets updated on > >> the > >> server not directly through an HTML form... Since it is only one so far > a > >> hand coded Dirty.mark(this) is not too evil. > >> > >> Sorry, talking to myself again. > >> -- > >> View this message in context: > >> > http://www.nabble.com/auto-dirty-and-widget-factory-tf4421187.html#a12899100 > >> Sent from the Wicket - User mailing list archive at Nabble.com. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/auto-dirty-and-widget-factory-tf4421187.html#a12917688 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
