On Friday 29 June 2007 12:12:28 D John Anderson wrote: > I suspect that committing every time the attribute is changed, i.e. > when you exit editing a field, might be a little better than > committing when you switch to as new item and wouldn't be that much > slower. Of course to really know, it's probably worth trying both. > > If I get some time to code it, maybe I could get you to help test it > for me.
Sure, no problem. Maybe I should also mention bug 8242, where there is a discussion of when recurrence change dialogs should be displayed and a notion of "edit session" is brought up. This sounds like it could have an impact on the possible solutions for that bug. > > I was suggesting having the timed commit as a fallback, but commit > > changes immediately if another item has been selected. Although it > > is possible that this would not be worth the extra complexity. > > I still need to look into this a bit, but I think that it might not > be very complicated. OK. I'd be glad to test it out. I was putting forward the ideas on that bug from a user's standpoint, without any knowledge of possible impacts and tradeoffs in terms of implementations. Davor _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
