yes but thats what component.setModelObject() does for you
On Sat, Mar 15, 2008 at 2:11 PM, James Carman <[EMAIL PROTECTED]> wrote: > On 3/15/08, Johan Compagner <[EMAIL PROTECTED]> wrote: > > you shouldn't really call modelChanging() or modelChanged() > > because your model is not changed at all > > what is changed is your internal counter (and you should use > > addStateChange()) > > > > But because of the way we now work, we dont do anything with the state > > changes objects > > anymore with the DiskPageStore (SecondLevelStore) when you call > > modelChanging() the version is incremented > > and that is all we need for the Store. > > > > the names of those 2 says it pretty much > > > > modelChanging() is when a model is about the change > > modelChanged() is when a model is changed. > > > > And modelChanging will add a statechange with the old model so that it > can > > set that back > > ofcourse if we would do that in modelChanged that wont work because the > old > > model is already gone. > > > > So, are supposed to call both? > > 1. Call modelChanging() > 2. Update model > 3. Call modelChanged() > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
