Friendlydeveloper.com

Posts Tagged ‘objective c’

I’ve recently been playing around with delegates and protocols and figured, it might be a good idea to create a simple example. The following article will show you, how you could implement a custom delegate into your own XCode project.

First, why would you want to do this? Well, there are a number of reasons. For instance, picture this: You have a class, that takes care of some calculations. Depending on how complicated these are, they can take up more or less time. Once the calculations are done, you want to send a feedback message to the class, that triggered the process. Using a custom delegate will allow you to receive that message without implementing the calling class into your calculations class. The big advantage is, that you will be able to use your calculations class in any class, send feedback message through the delegate and keep your code nice and clean.

Let’s get started, shall we?

In my sample project, I start off with a “View-based Application” template. It will give me the basic view hierarchy I need and I can get right to the fun part

I create a new “Objective-C” class (subclass of NSObject), name it “DelegateClass” and add it to my project. I now got two new files: DelegateClass.h and DelegateClass.m. Now I can start creating my delegate right away.

First, I want to add a protocol for my delegate. The protocol will contain the feedback method:

@protocol MyCustomDelegate <NSObject>

- (void)delegateSentFeedback;

@end

Now, I create an instance of my delegate inside @interface:

@interface DelegateClass : NSObject {
    id<MyCustomDelegate>    delegate; //create instance
}

I also need a method, that will do something. Therefore I name it “doSomething”:

- (void)doSomething;

Finally, I add @property for the delegate, so it can be assigned from any class:

@property (assign) id<MyCustomDelegate> delegate; //@property, so delegate can be assigned from any class #importing "MyCustomDelegate.h"

Inside DelegateClass.m I need to do two things:
Synthesize the delegate:

@synthesize delegate;

and add the doSomething method:

- (void)doSomething {
    if (delegate != nil && [delegate respondsToSelector:@selector(delegateSentFeedback)]) { //only trigger method IF delegate has been assigned and the method has been implemented into the target class

        //do something and then send callback message
        for (int i = 0; i < 10000; i++) {
            printf("I'm busy, I'm doing something");
        }
        [delegate performSelector:@selector(delegateSentFeedback)];
    }
}

The IF-Statement will make sure, that the delegate has been assigned from the calling class and that the calling class will implement the feedback method, named “delegateSentFeedback”.
Now, I move over to my viewController. I add a UIButton to start some process upon “TouchUpInside”. I connect it to an IBAction and end up with something like this:

- (IBAction)startProcessAction:(id)sender {
    DelegateClass *class = [[DelegateClass alloc] init];
    class.delegate = self; //IMPORTANT: if you don't assign the delegate, the feedback method will NOT be triggered!
    [class doSomething]; //start process
    [class release];
}

Btw, let’s not forget to #import “DelegateClass.h” into our ViewController’s .h file!
Last, but not least I implement the delegate feedback method, defined inside DelegateClass.h

- (void)delegateSentFeedback {
    //the process is done. let's show a simple UIAlertView
    UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@"Success" message:@"The process is done! Delegate has successfully sent feedback" delegate:self cancelButtonTitle:@"OK" otherButtonTitles:nil, nil];
    [alert show];
    [alert release];
}

The feedback method will show an UIAlertView, once “doSomething” method inside DelegateClass.m has reached the bottom.
Piece of cake, right?


Feel welcome to grab the sample project here, play with it, add new feedback methods and most importantly HAVE FUN!

In case you’ve ever played around with a sectioned UITableView and tried to delete rows from it, you’ve most likely experienced a crash once in a while.

When you read the console log, most of the time you find an entry similar to this one:

*** Terminating app due to uncaught exception ‘NSInternalInconsistencyException’, reason: ‘Invalid update: invalid number of sections.  The number of sections contained in the table view after the update (0) must be equal to the number of sections contained in the table view before the update (1), plus or minus the number of sections inserted or deleted (0 inserted, 0 deleted).’

Usually, your code for deleting stuff from your UITableView will look like this:

- (void)tableView:(UITableView *)tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath *)indexPath {

if (editingStyle == UITableViewCellEditingStyleDelete) { //let's delete something from our table
//IMPORTANT - modify data source BEFORE deleting rows from the table
[mySourceArray removeObjectAtIndex:indexPath.row]; //we assume, that mySourceArray is a NSMutableArray we use as our data source

[tableView beginUpdates];

[tableView deleteRowsAtIndexPaths:[NSArray arrayWithObject:indexPath] withRowAnimation:UITableViewRowAnimationFade];

[tableView endUpdates];

}

Now, things can get a bit more complicated when using a sectioned UITableView. In my case, I’ve been using a NSMutableArray (filled with NSDictionaries) as data source.
It looked like this:

NSMutableArray ->

……….-> NSDictionary:

………………..-> “headerTitle”: “A”

………………..-> “rowValue”: “RowValue1″, “RowValue2″, etc…

………..-> NSDictionary:

…………………-> “headerTitle”: “B”

…………………-> “rowValue”: “RowValue1″, “RowValue2″, etc…

etc,…

As you can see, a datasource like that is just a bit more complex than values directly inside a NSMutableArray.

In order to avoid the crash mentioned above, I had to make sure, that I only deleted rows from my table, when there were still OTHER rows left inside the same section. In case the row I wanted to remove was the last one within a section, I had to remove the entire section. Btw, that’s exactly what the crash log said

Here is my method again, this time with the needed modification:

- (void)tableView:(UITableView *)tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath *)indexPath {

if (editingStyle == UITableViewCellEditingStyleDelete) { //let's delete something from our tableNSDictionary *dict = [mySourceArray objectAtIndex:indexPath.section];

NSArray *array = [dict objectForKey:@"rowValue"];

int arrayCount = [array count]; //get the current count of the array
if(arrayCount == 1){ //we are removing the last item from this section - remove the ENTIRE section!

[tableView beginUpdates];

[tableView deleteSections:[NSIndexSet indexSetWithIndex:indexPath.section] withRowAnimation:UITableViewRowAnimationFade];
    [tableView endUpdates];
}
else { //just delete the row, since we've got more rows left inside this section
    [tableView beginUpdates];
    [tableView deleteRowsAtIndexPaths:[NSArray arrayWithObject:indexPath] withRowAnimation:UITableViewRowAnimationFade];
    [tableView endUpdates];}

}

Hope, you find this helpful. Feel welcome to leave a comment.

Cheers.

Hello everyone,

I’ve recently been playing with UILocalNotifications and really love them. When Apple first introduced Remote notifications (aka. push notifications), they were a real treat to both developers and users. Applications could receive information, even though they were not running at that time. However, it was (still is) a bit painful to implement them. You need to create certificates, run your own server or sign up with some company, that does the message forwarding for you.

Now, in case you only want to remind your users of something or allow them to schedule an event inside your app, UILocalNotifications are what you’ve been looking for. They are quite easy to set up and you don’t have to hassle with certificates, etc…

I’ve decided to release a little class, that easily allows you to schedule an event, delete a specific event or simply delete all events.

Ok, here we go:

My UILocalNotificaionsWrapper class consists of 3 different methods:

+ (void)addLocalNotification:(int)year:(int)month:(int)day:(int)hours:(int)minutes:(int)seconds:(NSString*)alertSoundName:(NSString*)alertBody:(NSString*)actionButtonTitle:(NSString*)notificationID;

+ (void)cancelLocalNotification:(NSString*)notificationID;

+ (void)cancelAllLocalNotifications;

The first method is the most complex one and allows you to submit several different values to customize your notification event:

• year (integer) – e.g. 2011
• month (integer) – e.g. 4 (April)
• day (integer) – e.g. 29
• hours (integer) – e.g 10 (= 10 am) – use 22 (military time) for 10 pm
• seconds (integer) – e.g. 0
• alertSoundName (NSString) – . e.g. nil to use custom sound name or @”NameOfTheSoundInsideYourAppBundle.wav”
• alertBody (NSString) – e.g. @”This is a LocalNotification”
• actionButtonTitle (NSString) – e.g. @”view” – This will appear on the button, when your local notification fires
• notificationID (NSString) – e.g. @”12345″  (has to be unique. you could keep track of your IDs inside an array, dictionary or SQLite database

Now you can simply make a call like this to schedule a new event:

[UILocalNotificationWrapper addLocalNotification:2011 :4 :4 :19 :17 :0 :nil :@"This is a LocalNotification!":@"View":@"12345"];

In order to delete the notification you just scheduled, you could make a call like this:

[UILocalNotificationWrapper  cancelLocalNotification:@"12345"];

Finally, to delete all scheduled notifications:

[UILocalNotificationWrapper cancelAllLocalNotifications];

One more thing…

Don’t forget to add #import “UILocalNotificationWrapper.h” inside the class you are making the calls from and always test on your device (UILocalNotifications don’t work on the simulator)

Grab the source file here and enjoy

Feedback always welcome.

 

In my previous blog entry I wrote about Creating a multi page PDF document on iPhone/iPod Touch/iPad with encryption.

One of my readers described a problem, that caused his newly created PDF file to contain strange/weird characters. He actually tried to open an existing PDF document and added a watermark image to every single page.

After doing some research on the internet, I found out, that this issue is quite common. In fact, it has been around for quite some time (2 + years – give or take). Unfortunately, Apple hasn’t yet introduced a fix.

So, I did some more digging and read up on 3rd party libraries. Using those libraries, you can actually create/modify a PDF document without the above issues. Bad news is, that Apple might not approve your app. It’s really up to every single developer, whether he/she wants to go for a solution like that or not. Since I can not simply ask Apple, I decided to rule out that option.

So, what other solutions are left? Well, it certainly depends on the case, but in my and my reader’s situation, the following hack worked:

1. Open the PDF-document
2. Render it into an offscreen UIView
3. Create a new PDF document
4. Paste the image and add additional information (text/pictures)
5. Save the new PDF document.

There is of course one major downside. The new PDF document no longer contains the real text, but an image displaying the text. This might turn into a problem, if zooming or copy/paste actions are needed later. However, for just reading, this works great.

For those, who want to see this in action, I’ve uploaded a demo project. Feel welcome to grab it here.

If you’re developing an iPhone, iPod Touch or iPad app and get stuck, the internet definitely is your friend. You can find lots of helpful resources on different coding forums or sites like this one.

However, sometimes the information there is just not enough or you might have an idea and don’t know how to get started.
Well, this is where our new service might come in handy.

As of now, you can schedule a 1 on 1 session with one of our coders and he/she will help you.

Sessions will be held via iChat and our coder will share his/her screen with you. This way, you can exactly see what is going on and therefore learn much faster. If you like, we’ll also do a screen recording for free, so you can watch it later again and again at no extra cost.

Some session examples:

* Your first app: How to build proper view hierarchy.
* SQLite database programming.
* Server communication – How to submit and retrieve data from a webserver.
* In app purchases.
* Push notifications.
* 3D game development
* etc…

Our live coding sessions are available in both english and german language.

If you’re interested, just send an email to lindmandesignsupport[at]me.com and we’ll provide you with details on pricing, etc…

Implementing Apple push notifications into your iPhone/iPod Touch or iPad app can be quite the challenging task. You really have to pay close attention to the official docs when setting it up and even then it might not work right out of the box.

If you’re new to APNS, you might want to check out the tutorials, I mentioned in one of my previous posts:

http://blog.boxedice.com/2009/07/10/how-to-build-an-apple-push-notification-provider-server-tutorial/
and
http://mobiforge.com/developing/story/programming-apple-push-notification-services

I can only repeat myself by saying, that these tutorials really rock and should definitely get you started.

If you don’t plan on running your own server, check out Urban Airship. They currently offer two different plans, which should perfectly fit your needs.

However, implementing APNS on your own server is most fun, as you’re likely going to face some issues

Rule #1, if nothing you tried so far works: Get some open source package and learn from the professionals: EasyAPNS is exactly what you might want to check out in this kinda situation.

Don’t forget to watch the video tutorial, which can be found right on the landing page.

Some additional hints and suggestions:

If your iPhone/iPod Touch/iPad app communicates with your server (maybe via php scripts), check out ASIHTTPRequest. This is some awsome package, that you can easily integrate into your existing XCode project. It’s perfect for contacting your server via POST requests. However, ASIHTTPRequest can do much more – just check out the official docs, which can be found on the developer’s website.

If you’re testing push notifications with your beta testers, make sure that you’re using the correct APNS certificate on your server. By correct I mean: Development certificate or Production certificate. In case you followed the tutorials above, you probably created both. In order to clear things up, check out the steps below:

• If your iPhone/iPod Touch/iPad app communicates with your server (maybe via php scripts), check out ASIHTTPRequest. This is some awsome package, that you can easily integrate into your existing XCode project. It’s perfect for contacting your server via POST requests. However, ASIHTTPRequest can do much more – just check out the official docs, which can be found on the developer’s website.
• If you’re testing push notifications with your beta testers, make sure that you’re using the correct APNS certificate on your server. By correct I mean: Development certificate or Production certificate. In case you followed the tutorials above, you probably created both. In order to clear things up, check out the steps below:

1. Find your Provisioning certificate and the AdHoc one, you are using for your beta testers: Open up XCode and go to “Window”->”Organizer”. Now click on your Provisioning certificate, then right click -> “Reveal in Finder”. Do the same for your AdHoc certificate.
2. Open up both files with TextEdit (DON’T EVER CHANGE ANYTHING IN THERE!!!) and look for the following string: “Environment”.
3. Right below you should see either “Development” or “Production”.
4. If you want your beta testers to receive push notifications and their AdHoc certificate says “Production”, you now know that you will have to use the APNS Production certificate on your server. Otherwise push messages won’t get delivered.

Happy pushing

NSFileManager offers a convenient way to write images to and load them from the documents directory.

If you’re frequently doing that in your project, I suggest to wrap up NSFileManager support in three simple methods:

//saving an image

- (void)saveImage:(UIImage*)image:(NSString*)imageName {

NSData *imageData = UIImagePNGRepresentation(image); //convert image into .png format.

NSFileManager *fileManager = [NSFileManager defaultManager];//create instance of NSFileManager

NSArray *paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES); //create an array and store result of our search for the documents directory in it

NSString *documentsDirectory = [paths objectAtIndex:0]; //create NSString object, that holds our exact path to the documents directory

NSString *fullPath = [documentsDirectory stringByAppendingPathComponent:[NSString stringWithFormat:@"%@.png", imageName]]; //add our image to the path

[fileManager createFileAtPath:fullPath contents:imageData attributes:nil]; //finally save the path (image)

NSLog(@"image saved");

}

//removing an image

- (void)removeImage:(NSString*)fileName {

NSFileManager *fileManager = [NSFileManager defaultManager];

NSArray *paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES);

NSString *documentsDirectory = [paths objectAtIndex:0];

NSString *fullPath = [documentsDirectory stringByAppendingPathComponent:[NSString stringWithFormat:@"%@.png", fileName]];

[fileManager removeItemAtPath: fullPath error:NULL];

NSLog(@"image removed");

}

//loading an image

- (UIImage*)loadImage:(NSString*)imageName {

NSArray *paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES);

NSString *documentsDirectory = [paths objectAtIndex:0];

NSString *fullPath = [documentsDirectory stringByAppendingPathComponent:[NSString stringWithFormat:@"%@.png", imageName]];

return [UIImage imageWithContentsOfFile:fullPath];

}

Now, you can easily save an image like:

[self saveImage: myUIImage: @"myUIImageName"];

or load it like:

myUIImage = [self loadImage: @"myUIImageName"];

or remove it like:

[self removeImage: @"myUIImageName"];

Usually, iPhone apps are built using some kinda hierarchy:

• ->AppDelegate
• ->-> RootViewController
• ->->->OtherViewController(s)
• ->->->->Views

On various occasions, you might want to get some information from your AppDelegate (e.g. values, array infos, etc…).

You might already know, that there is a simple line of code, which gives you access to your AppDelegate:

AppDelegate *mainDelegate = (AppDelegate*)[[UIApplication sharedApplication]delegate];

If you need access to your AppDelegate only once or twice in a View or ViewController, this is the best way to go. However, if you have several methods in your View or ViewController and some of them need AppDelegate access, you always have to repeat the above line of code first.

In order to avoid that, there is a simple way, to permanently implement AppDelegate access in your View or ViewController:

//this example assumes, that we are using a ViewController

//inside .h file

//below #import lines

@class AppDelgate;

@interface MyViewController : UIViewController {

AppDelegate *mainDelegate;

}

//@property (nonatomic, retain) AppDelegate *mainDelegate; //error correction here - no need to @property

@end

//inside .m file

//below #import lines

#import "AppDelegate.h"

@implementation MyViewController

@synthesize mainDelegate;

- (void)viewDidLoad {

mainDelegate = (AppDelegate*)[[UIApplication sharedApplication]delegate];

}

- (void)dealloc {

//[mainDelegate release]; //error correction here - the mainDelegate object does not need to be released, since we do not call alloc init on it.

[super dealloc];

}

//now you have access to your AppDelegate in every method

//example: we assume, that our AppDelegate holds three different integer values we want to grab

- (void)methodA {

int numberA = mainDelegate.numberA;

}

- (void)methodB {

int numberB = mainDelegate.numberB;

}

- (void)methodC {

int numberC = mainDelegate.numberC;

}

As you can see, it’s slightly more work to implement AppDelegate access than just using that single line of code over and over again. However, in my opinion it’s well worth the time, especially if your .m file holds many methods.

Your code appears much cleaner that way.

[IMPORTANT: The information below is no longer up to date. Apple does now no longer allow you to use UIGetScreenImage(). Instead you need to use a different method. You can read about that on the official developer forum, located at developer.apple.com]

Not too long ago Apple decided to make on of their private APIs public. They now officially allow developers to make use of a very handy method:

+ (UIImage *)imageWithScreenContents;

Before they released it, grabbing screen contents could be a real nightmare. In some (rare) situations, it was pretty much impossible.
When you were using lots of openGL stuff in your project and wanted to grab the current state of your screen, you had to use glReadPixels();
This worked fine most of the time, but when you were dealing with transparency, it could make you pull your hair off

Anyways, those times are finally over.

To make use of this API, simply add the following lines to the .m file where you want to call it later:

//right below #import lines
CGImageRef UIGetScreenImage();
@interface UIImage (ScreenImage)
+ (UIImage *)imageWithScreenContents;
@end

@implementation UIImage (ScreenImage)
+ (UIImage *)imageWithScreenContents
{
    CGImageRef cgScreen = UIGetScreenImage();
    if (cgScreen) {
        UIImage *result = [UIImage imageWithCGImage:cgScreen];
        CGImageRelease(cgScreen);
        return result;
    }
    return nil;
}
@end

Now you can easily do something like this:

- (void)saveScreenshotToPhotolibrary {
	UIImageWriteToSavedPhotosAlbum([UIImage imageWithScreenContents], nil, nil, nil);
}

Congrats! You just saved an image with screen contents to your iPhone photo library.