On Mar 15, 2013, at 6:38 PM, Quincey Morris wrote:
>> Am I wrong on that? I don't think I am, so I guess I'll keep on trucking
>> with the above code.
>
> The only thing that springs to mind is that *perhaps* it's more correct to
> think of the formatter as a validator of input structure, rathe
On Mar 15, 2013, at 18:07 , Seth Willits wrote:
> So my questions:
>
> 1) I see no way for a combo box to have a "default value" if say the
> formatter returns nil
> 2) I see no way for a formatter to have a "default value" if it can't convert
> a value.
>
>
> Am I wrong on that? I don't thi
There's a possibility I just can't see what's in front of me. I have a combo
box where the pulldown has some possible values (2, 4, 8), but the user should
be able to enter anything from 1-8, so I've added a number formatter with a min
and max value etc. The user, though can delete the text ent
Hi Timothy,
What I would try to do is, break in the debugger on viewDidLoad of your primary
view controller, and issue the following:
po [[self view] recursiveDescription]
It will print out the view hierarchy so that you can begin to deduce what the
actual problem is. Some mistakes that I seem
Hi Laurent,
when I faced a similar problem - in my case I needed to filter data acquired
fromCoreData in a TableView for a field value that wasn't part of the model,
but existed as an ivar in the NSManagedObject subclass - I used the following:
[self.sessionController setFilterPredicate:[NSPred
Thank you to everyone whose helped me with this problem. I now have the
solution I needed, and (as usual) I've learned a whole lot that will be useful
in the future.
As always, this is an incredibly useful resource!
On 15 Mar 2013, at 02:16, Seth Willits wrote:
> On Mar 14, 2013, at 11:22 AM
