Re: an interesting delegate design issue raised by IB...
Re: an interesting delegate design issue raised by IB...
- Subject: Re: an interesting delegate design issue raised by IB...
- From: Ondra Cada <email@hidden>
- Date: Wed, 12 Sep 2001 20:30:44 +0200
Michael,
>
>>>>> Michael B. Johnson (MBJ) wrote at Wed, 12 Sep 2001 10:57:57 -0700:
MBJ> >Of course, you can send those notifications using NSPostWhenIdle, which
MBJ> >would easily solve this problem (but not some more elaborated ones).
MBJ>
MBJ> like what? I'm interested - I wouldn't do it this way, but I'm
MBJ> interested in what problems might arise from doing it this way.
Like if I (as a programmer) _for any reason_ don't _want to_ redisplay the
change immediately.
Frankly, I can't imagine none such reason just now. My programming
experience just kind of hints that *if* the API would not make that possible,
then some such reason would occur one day ;)
MBJ> Ooh, I really don't like that. It would be too easy to have things get
MBJ> out of sync.
As you perhaps noticed, with API I am for flexibility, even if it happens to
be dangerous when not used properly. That's just my opinion, of course (but
I guess Brad Cox had the very same idea when designed ObjC!).
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc