Yes probably in most cases. One can send an object and a NSDictionary
(userInfo) though too. So there are some implied options. I was about to
over-use my userInfo ;)
On Tue, Jan 26, 2016 at 11:46 AM Alex Zavatone wrote:
> Shouldn't the notification be as dumb as possible and let the notificatio
Shouldn't the notification be as dumb as possible and let the notification
receiver/processor handle any decisions on what to process or read from?
On Jan 26, 2016, at 10:37 AM, Clark Cox wrote:
> The notification’s userInfo *must* be a dictionary, trying to force it to be
> something else is
I agree with you there in terms of passing the data in the notification.
I've requested that the developer in charge of some of the appDelegate
backend allow for the explicit data request. It's an extra call or two, but
keeps the pipeline known and clean.
On Tue, Jan 26, 2016 at 10:37 AM Clark Cox
The notification’s userInfo *must* be a dictionary, trying to force it to be
something else is just asking for trouble. You could create a dictionary that
contains your array of dictionaries if you want to be able to pass it through
an NSNotification.
That said, IMHO, this use of notifications
That makes perfect sense - thanks. I forgot about the userInfo type!
On Tue, Jan 26, 2016 at 10:31 AM Roland King wrote:
>
> > On 26 Jan 2016, at 23:12, Eric E. Dolecki wrote:
> >
> > I have a control which takes an array of dictionaries to construct it's
> UI
> > (as a distinct method).
> >
>
> On 26 Jan 2016, at 23:12, Eric E. Dolecki wrote:
>
> I have a control which takes an array of dictionaries to construct it's UI
> (as a distinct method).
>
> Now I'd like to add a notification to supply the data as well. I'd like to
> pass the data as userInfo.
>
> When constructing the obse