Try this:
[[UIApplication sharedApplication] setNetworkActivityIndicatorVisible:YES];
Archive for the 'iPhone' Category
So you might have spent some time trying to figure out how to do a fade transition on iPhone. You probably found sample code and doc for things like curl and flip but not fade in/out, right? Well, it’s actually pretty simple:
[UIView beginAnimations:nil context:NULL];
[UIView setAnimationDuration:1.0];
someView.alpha = 0.1;
[UIView commitAnimations];
Bam. You just faded from whatever prior alpha value was set on someView to 0.1 (10%) opacity. The setAnimationDuration method takes a float value in seconds. You could go all the way to 0 to hide it, or set it higher later to fade it back in. This means you can do something like this:
[UIView beginAnimations:nil context:NULL];
[UIView setAnimationDuration:0.5];
someImageView.alpha = 0.0;
[UIView commitAnimations];
[someImageView setImage: [UIImage imageNamed:@"anotherImage.png"]];
[UIView beginAnimations:nil context:NULL];
[UIView setAnimationDuration:0.5];
someView.alpha = 1.0;
[UIView commitAnimations];
to create a fade transition from one image to the next. The total time from hiding one image to seeing the next would be 1 second, in this case.
Finally, we have a functional build of BM out on the App Store. I have no earthly clue why Drew and I never ran into the odd primary key bug prior to the release of 1.0. Bleh. Download the update and revise your review, por favor.
So people have already started pirating CastCatcher. It’s 3 freaking dollars. :[
We pushed BillMinder 1.0 to Apple a few days back, while it was in review, firmware 2.1 hit. We were using it on our phones but already had our bills setup so it seemed to work well. In reality, adding new bills (well, adding new anything that resulted in a database row being created failed). It ends up that the function sqlite3_last_insert_rowid returned zero instead of the pk for the last inserted row after the first call — bad times. This meant strange things happened (like bills being duplicated or disappearing, etc.).
Our “fix” was simply to select pk from table order by pk desc and use that value. It seems to work well — we put in the change, fixed some other minor usability issues and BillMinder 1.01 is on its way to users. Talk about a headache. The moral of this story is test your software from a clean DB after a new firmware hits.
Update: This does not seem to be an issue w/ iPhone 2.1 but rather an issue that occurs after inserting 3 rows and calling sqlite3_last_insert_rowid 3 times, as far as I can tell
How I Roll