On Apr 28, 2012, at 6:21 PM, Keary Suska wrote:
> Are you updating the model data in a KVO-compliant way?
Bingo! Thanks for pointing that out, I kept looking at my connections in IB,
and forgot about the actual code.
So for future reference, my data model is an NSMutableArray. Instead of add
I have a follow up question.
One of the columns in the table shows a number (a float), and I have added a
min and max value property to my controller to filter the data in the table. I
could filter the data every time the user changes the min and/or max values but
that means I need to recreate
On Apr 29, 2012, at 6:24 PM, Koen van der Drift wrote:
> I have a follow up question.
>
> One of the columns in the table shows a number (a float), and I have added a
> min and max value property to my controller to filter the data in the table.
> I could filter the data every time the user cha
I've had the joy of trying to reassemble my app which a co worker improved last
week by moving it to storyboarding. What's popping up every now and then as I
try to wire views together are instant SIGABRTs with no indication why this is
happening.
I'm currently stuck going from a TableViewCont
On Apr 29, 2012, at 9:22 AM, Koen van der Drift
wrote:
> So for future reference, my data model is an NSMutableArray. Instead of
> adding objects by calling addObject, I need to call it as follows:
>
> - (void)addMyObject:(MyObject *)obj
> {
>NSMutableArray *temp = [self mutableArrayVal
On Sun, Apr 29, 2012 at 7:50 PM, Alex Zavatone wrote:
> I've had the joy of trying to reassemble my app which a co worker improved
> last week by moving it to storyboarding. What's popping up every now and
> then as I try to wire views together are instant SIGABRTs with no indication
> why thi
It sounds to me like your xib (nib) file has been "corrupted". For example,
it's possible that you have somehow destroyed, say, a link between an object
(view?) and its counterpart in your implementation or a link between an object
like a button or a textfield and it's IBAction.
I suggest that
I had the same thing Friday night or last night too.
I ended up creating a new TVC, moving pieces in one at a time and in one case,
it was the table cell name not matching.
Now, I've gotten an empty TVC to work, so it's move the pieces in one at a time
again.
There are no errors when I p
At least during development I do this to main.m
int main(int argc, char *argv[])
{
@autoreleasepool {
@try
{
return UIApplicationMain(argc, argv, nil,
NSStringFromClass([HIPAppDelegate class]));
}
@ca
On Apr 29, 2012, at 11:26 PM, Roland King wrote:
> At least during development I do this to main.m
>
> int main(int argc, char *argv[])
> {
> @autoreleasepool {
> @try
> {
> return UIApplicationMain(argc, argv, nil,
> NSStringFromClass([H
That's autogenerated code, came from the project template.
On Apr 30, 2012, at 11:33 AM, Alex Zavatone wrote:
>
> On Apr 29, 2012, at 11:26 PM, Roland King wrote:
>
>> At least during development I do this to main.m
>>
>> int main(int argc, char *argv[])
>> {
>> @autoreleasepool {
>>
Ahh. Well, I changed it back from HIPAppDelegate to AppDelegate and when the
SIGABRT happens, the catch isn't catching it. I set a breakpoint on NSLog and
it's never triggered.
Am I assuming too much here?
On Apr 29, 2012, at 11:35 PM, Roland King wrote:
> That's autogenerated code, came fr
I think I got it working thanks for the help!
On Apr 28, 2012, at 1:48 PM, Graham Cox wrote:
> Use NSNumberFormatter as correctly suggested. You can set its
> -positiveSuffix: string to "Days" and that's it. You're done.
>
> --Graham
>
>
>
>
>
> On 28/04/2012, at 2:41 PM, Rick C. wrote:
On Sun, Apr 29, 2012 at 8:00 PM, Don Quixote de la Mancha
wrote:
> Place some assertions as the very first executable lines in each of
> your subroutines. The chances are quite good that the cause of the
> SIGABRTs are executable quite a long time before the crashes actually
> happen.
...
> #incl
14 matches
Mail list logo
