[bug #3797] EOEditingContext, objectWillChange

[nobody]

=================== BUG #3797: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3797&group_id=99

Changes by: David Ayers <d.ayers@inode.at>
Date: Mon 07/07/2003 at 21:57 (Europe/Vienna)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | None                      | ayers


------------------ Additional Follow-up Comments ----------------------------
Sorry for the long delay in looking into this.  I tried to verify it a while 
back couldn't.  Now I had some time to dig deeper.

To which passages of the docs are you refering to?  I don't see any queing of a 
-processRecentChanges in any run loop (at least not through the standard 
methods: performSelector:target:argument:order:modes:, 
performSelector:withObject:afterDelay: or 
performSelector:withObject:afterDelay:inModes:)
during objectWillChange. (Testing with WO 4.5)

It is directly invoked from EOEditingContext-_processEndOfEventNotification: 
somewhere during EOEditingContext-saveChanges.  So, to me, our implementation 
seems correct.




=================== BUG #3797: FULL BUG SNAPSHOT ===================


Submitted by: dlatt                   Project: GNUstep                      
Submitted on: Thu 05/29/2003 at 09:58
Category:  gdl2                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  ayers                   Status:  Open                         

Summary:  EOEditingContext, objectWillChange

Original Submission:  EOEditingContext should (according to the docs) add an 
invocation of -processRecentChanges to the end of the current run loop.

This may probably be done like in EODelayedObserverQueue.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Mon 07/07/2003 at 21:57       By: ayers
Sorry for the long delay in looking into this.  I tried to verify it a while 
back couldn't.  Now I had some time to dig deeper.

To which passages of the docs are you refering to?  I don't see any queing of a 
-processRecentChanges in any run loop (at least not through the standard 
methods: performSelector:target:argument:order:modes:, 
performSelector:withObject:afterDelay: or 
performSelector:withObject:afterDelay:inModes:)
during objectWillChange. (Testing with WO 4.5)

It is directly invoked from EOEditingContext-_processEndOfEventNotification: 
somewhere during EOEditingContext-saveChanges.  So, to me, our implementation 
seems correct.



CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3797&group_id=99

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/