Skip to main content

UIPopoverController Tutorial For iPad with iOS8 Swift: iOS Programming

UIPopoverController Tutorial



UIPopoverController is similar to Action Sheet. it is also another cool and important tool, especially for the iPad. PopoverController is a nice way to present information to the user.A popover controller is nothing but a container which is used to display content on top of another content. UIPopoverController’s content is layered on top of your existing content in a special type of window.
In our Previous Tutorial, we have already completed UIActionSheet so if you have not then read out Action Sheet Tutorial.

Project Setup:

This Tutorial is built in Xcode 8.2.1 so if you have not update your Xcode, First Update Xcode. Now Open Xcode and create a new Single View Application. In product name, use PopoverTutorialDemo and then fill out the Organisation Name and Organisation Identifier with your customary values. Select Swift as Language and make sure you have select iPad style for Devices.


Make UIDesign:

Go to the Storyboard, drag a Button from the Object Library to the View Controller inside the Storyboard. Double-click the Button and give it a title of “Show PopOver” or whatever you want.

Make IBOutLayoutConnection for UIButton:

Open the Assistant Editor. Ctrl + drag from the Button to the ViewController class and create the following Action and Click on Connect.



add UIPopoverController variable in ViewController class. This variable will be used in the ShowPopOverMthod.
var popOverData = UIPopoverController()
Now, we will create a new viewController. Add a new File -> iOS -> Cocoa Touch -> Swift class and make it a subclass of UITableViewController. Select the “With XIB for user interface” checkbox and name the class UserDataViewController.



Update Xib User Interface:
Go to UserDatViewController.xib and select UITableViewCell from object Library and dragon to xib. Now select Cell and give the cell identifier name with “reuseIdentifier”.

Implement UserDataViewController Class:

Go to UserDataViewController.swift. Inside This Class update the class with following code. This code is simple because we are just trying to register the TableViewCell and update DataSource methods of TableView Protocol.
return 1 under the numberOfSections method.
return 10 under the tableView(_ tableView: UITableView, numberOfRowsInSection section: Int) method.
Uncomment tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell method.

import UIKit
class UserDataViewController:  UITableViewController{ 
//...




// in viewDidLoad method. self.tableView.register(UITableViewCell.self, forCellReuseIdentifier: "reuseIdentifier") //in tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell var cell = tableView.dequeueReusableCell(withIdentifier: "reuseIdentifier", for: indexPath) as? UITableViewCell cell?.textLabel?.text = "This is User \(indexPath.row)'s cell"
}
Now come back to ViewController class and add this code inside ShowPopOverMethod.
import UIKit
class ViewController:  UIViewController{ 
//...
let PopoverView = UserDataViewController(nibName: "UserDataViewController", bundle: nil)
self.popOverData = UIPopoverController(contentViewController: PopoverView)
self.popOverData.present(from: sender.frame, in: self.view, permittedArrowDirections: .down, animated: true) 
}

Now Build and run the App and click on “Show PopOver” button. Great New PopOver View will be Appear.





For your reference, you can download the complete Xcode project from here. Again, leave me to comment if you have any questions.

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...