On Sep 14, 2012, at 10:49 PM, Steve Steinitz <stein...@datatactics.com.au> wrote:
> Hi Ken, > > Thanks for your quick reply. > > On 15 Sep 12, at 3:16pm, Ken Thomases wrote: > >> No offense, but this seems like a terrible design. And your KVO hack method >> screams of papering over a bug. > > No offense but none of your criticisms seem to hold water. I might address > them individually after I see if anyone can offer any help with my actual > question, rather than cluttering the thread now. Ken is right. A shift is an object with a known number of instances per employee. You've those instances and splayed out thir properties as methods on the employee. It would be far easier to have a -[Employee shiftForDayOfWeek:] method that returns a Shift instance, and put all your shift-specific properties on that object. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
