| Hey Chuck,
/Library/Receipts tells me I'm on the 5.3.3 update.
I have been running with DebugGroupMultithreading for a few days now, and nothing seems to have changed, so I assumed everything was ok there, but it could just be that I set things up wrong. I just added the following lines to my Application constructor:
NSLog.debug.setAllowedDebugLevel(NSLog.DebugLevelInformational); NSLog.allowDebugLoggingForGroups(NSLog.DebugGroupEnterpriseObjects | NSLog.DebugGroupMultithreading);
Should that do it, or is there something else I need to do?
Otherwise, I will go through and clean out anything anywhere that overrides a setter or getter and changes the data being set/get, and I'll see if that makes a difference.
Thanks for the suggestions.
Mark
On Apr 19, 2007, at 3:42 PM, Chuck Hill wrote: Also, are you on the latest WO version?
On Apr 19, 2007, at 12:33 PM, Steven Mark McCraw wrote:
Hi Chuck,
Thanks for the response. I'm 99.9% sure that I'm locking properly, and the only EOF commandment I might possibly be breaking is the one that says:
"Don't change the behavior of methods that EOF uses. For example, do not override to-many relationships to return a sorted list of the related objects. Make another method to do this."
I'm not overriding to-many relationship methods, but I do sometimes override setters. For example, I might override a particular attribute so that I can make a record of the time that the attribute was changed. Moreover, there are places that I override accessors for formatting purposes. An example of this would be overriding a phoneNumber() method to add formatting to the returned string, or overriding a setPhoneNumber method so that it strips formatting off. Are these things problematic?
Thanks, Mark
On Apr 19, 2007, at 12:50 PM, Chuck Hill wrote:
This pretty much means one of two things:
1. You are not locking properly
2. You are violating EOF commandments
Chuck
|