[chandler-users] partial sync of events problem

[Mimi Yin]

Yes, I'm asking if we can *not sync* the currently selected item *if*  
the user has their focus in a field of the detail view.

On Sep 7, 2007, at 1:14 PM, Jeffrey Harris wrote:

> Hi Mimi,
>
>> I can't remember, was there ever a specific reason to *not* commit
>> items if keyboard focus is in one of the detail view fields for that
>> item?
>
> I'm not really understanding your question, here.
>
> There are actually 2 different things at work here: changes to an
> attribute don't get applied (different from committing) until a  
> field is
> left.  When the change gets applied, it's supposed to also get  
> committed.
>
> There's been talk of applying and committing changes in a field  
> every 5
> minutes or something like that, that would reduce the number of times
> syncing happens in mid-edit, but it could still happen.
>
>> In other words, the New Event item would never be committed so long
>> as Esther's cursor was still in the Title field.
>
> This seems different from your question above.  Currently, the new  
> item
> gets committed when it's created, so there's not really a window to  
> not
> commit new items.  We could conceivably add complexity to sharing to
> avoid syncing items that are somehow flagged as "just created, not  
> fully
> baked yet", I suppose, but it'd be hard to make that work.
>
> Sincerely,
> Jeffrey
> _______________________________________________
> chandler-users mailing list
> chandler-users at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/chandler-users