Skip to main content

How To Animating UITableView Cells In Objective C

Animating UITableView Cells



In this quick tutorial I’d like to show you how to add a simple but interesting effect to your UITableView using with just a few lines of code.

I love Core Animation and I think it is a fantastic instrument that allows us to easily achieve some interesting effects with almost no effort. So, in this experiment we are going to animate the cells of a table through some easy settings over the cells’ layers.

First Download this Project - https://github.com/ariok/TB_TableAnimation/archive/master.zip

Project description

I’ve decided to apply just a 3D rotation on the Z axis to the cells when they are displayed. Anyway, it will be really simple to change my settings creating something that fits your needs.

Let’s code

Now open the file TableViewController.m. You’ll notice quite easily it’s a pretty standard configuration. In fact, we’ve just implemented the basic TableViewController’s delegate and datasource.

Now focus on the function tableView:WillDisplayCell:ForRowAtIndexPath:

This is part of the protocol UITableViewDelegate and it’s called just before a cell is displayed on the screen.

Since we want to animate the cells as soon as they are displayed, this is the right place where to work.

Here’s the complete code for the function:





//This function is where all the magic happens
-(void)tableView:(UITableView *)tableView willDisplayCell:(UITableViewCell *)cell forRowAtIndexPath:(NSIndexPath *)indexPath{
    
    
    //1. Setup the CATransform3D structure
    CATransform3D rotation;
    rotation = CATransform3DMakeRotation( (90.0*M_PI)/180, 0.0, 0.7, 0.4);
    rotation.m34 = 1.0/ -600;
    

    //2. Define the initial state (Before the animation)
    cell.layer.shadowColor = [[UIColor blackColor]CGColor];
    cell.layer.shadowOffset = CGSizeMake(10, 10);
    cell.alpha = 0;
    
    cell.layer.transform = rotation;
    cell.layer.anchorPoint = CGPointMake(0, 0.5);
    
    
    //3. Define the final state (After the animation) and commit the animation
    [UIView beginAnimations:@"rotation" context:NULL];
    [UIView setAnimationDuration:0.8];
    cell.layer.transform = CATransform3DIdentity;
    cell.alpha = 1;
    cell.layer.shadowOffset = CGSizeMake(0, 0);
    [UIView commitAnimations];
    
}
In Step 1 we instruct a CATransform3D to perform a rotation over the Y and Z axis (Check the first part of this tutorial if you need more information about 3D and Core Animation).

With Step 2 we define the initial state of the cell. In that case we are adding some shadows (for the glory, as this is barely visible during the animation) and we update the layer transform matrix using the rotation created  in Step 1.

We then set the anchor point at X 0.0 and Y 0.5 to achieve a rotation around the left side of the cell.

The last Step 3, resets the cell to its original state through an animation.
Essentially we use the helper function of UIView beginAnimations:context to update the values of the cell’s layer performing the animation.

You have other ways to perform this animation, but this is just the easiest that also allows us to choose a duration.

In this particular function we reset the transformation to CATransform3D Identity, the background color to white, the shadow to 0 and the alpha to 1.

So we take advantage of the interpolation between the state of step 2 and the state of step 3 to guide the animation and achieve an original effect.

Thank you for reading.

Comments

Popular Posts

Reloading UITableView while Animating Scroll in iOS 11

Reloading UITableView while Animating Scroll Calling  reloadData  on  UITableView  may not be the most efficient way to update your cells, but sometimes it’s easier to ensure the data you are storing is in sync with what your  UITableView  is showing. In iOS 10  reloadData  could be called at any time and it would not affect the scrolling UI of  UITableView . However, in iOS 11 calling  reloadData  while your  UITableView  is animating scrolling causes the  UITableView  to stop its scroll animation and not complete. We noticed this is only true for scroll animations triggered via one of the  UITableView  methods (such as  scrollToRow(at:at:animated:) ) and not for scroll animations caused by user interaction. This can be an issue when server responses trigger a  reloadData  call since they can happen at any moment, possibly when scroll animation is occurring. Example of s...

What are the Alternatives of device UDID in iOS? - iOS7 / iOS 6 / iOS 5 – Get Device Unique Identifier UDID

Get Device Unique Identifier UDID Following code will help you to get the unique-device-identifier known as UDID. No matter what iOS user is using, you can get the UDID of the current iOS device by following code. - ( NSString *)UDID { NSString *uuidString = nil ; // get os version NSUInteger currentOSVersion = [[[[[UIDevice currentDevice ] systemVersion ] componentsSeparatedByString: @" . " ] objectAtIndex: 0 ] integerValue ]; if (currentOSVersion <= 5 ) { if ([[ NSUserDefaults standardUserDefaults ] valueForKey: @" udid " ]) { uuidString = [[ NSUserDefaults standardDefaults ] valueForKey: @" udid " ]; } else { CFUUIDRef uuidRef = CFUUIDCreate ( kCFAllocatorDefault ); uuidString = ( NSString *) CFBridgingRelease ( CFUUIDCreateString ( NULL ,uuidRef)); CFRelease (uuidRef); [[ NSUserDefaults standardUserDefaults ] setObject: uuidString ForKey: @" udid " ]; [[ NSUserDefaults standardUserDefaults ] synchro...

Xcode & Instruments: Measuring Launch time, CPU Usage, Memory Leaks, Energy Impact and Frame Rate

When you’re developing applications for modern mobile devices, it’s vital that you consider the performance footprint that it has on older devices and in less than ideal network conditions. Fortunately Apple provides several powerful tools that enable Engineers to measure, investigate and understand the different performance characteristics of an application running on an iOS device. Recently I spent some time with these tools working to better understand the performance characteristics of an eCommerce application and finding ways that we can optimise the experience for our users. We realised that applications that are increasingly performance intensive, consume excessive amounts of memory, drain battery life and feel uncomfortably slow are less likely to retain users. With the release of iOS 12.0 it’s easier than ever for users to find applications that are consuming the most of their device’s finite amount of resources. Users can now make informed decisions abou...