How about committing after the user navigated away from the *item* that
was modified, not on every attribute?
But this would probably also need a timer that would commit anyways after
a minute if no further modifications were made but the user never
navigated away.
(C.f. comment #9 in the bug.)
Davor
On Thu, 28 Jun 2007, D John Anderson wrote:
Hi:
I'm working on bug #9507 which is caused by someone editing the title of an
event. These changes aren't committed as they occur for performance reasons.
I'm considering a few simple options:
1) Commit every X seconds (say 5 or 10) if there are changes that need to to
be saved
2) Commit every time the attribute editors set an attribute.
I suspect option 1 would work a little better than option 2. I was curious to
know what you guys thought.
Also, Andi, is there an API to know if there are changes to commit in the UI
view?
John
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
