Difference Segue Excute in Container View to AVPlayerViewController

Posted on Edited on

1. Difference Segue Excute in Container View to AVPlayerViewController

Demo on GitHub

Objective-C this method won’t be execute.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
// In Swift should check the method, even user don't tap the cantainer view.
// But in Objective-C,  *** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', 
// reason: 'Could not instantiate class named AVPlayerViewController'
- (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender {
    
    // set up the player
    if ([segue.identifier  isEqual: @"videoSegue"]) {
        
        NSString *path = [[NSBundle mainBundle] pathForResource:@"yishengsuoai" ofType:@"mp4"];
        NSURL *url = [[NSURL alloc] initFileURLWithPath:path];
        
        AVPlayerViewController *vc = segue.destinationViewController;
        vc.player = [AVPlayer playerWithURL:url];
    }

}
1
2
3
4
5
6
7
8
9
10
11
12
13
14
// BEGIN avkit_ios_config
override func prepareForSegue(segue: UIStoryboardSegue, sender: AnyObject?)
{
    if segue.identifier == "videoSegue"
    {
        // set up the player
        let videoURL = NSBundle.mainBundle().URLForResource("TestVideo",
                                                       withExtension: "m4v")
        let videoViewController =
                   segue.destinationViewController as! AVPlayerViewController
        videoViewController.player = AVPlayer(URL: videoURL)
    }
}
// END avkit_ios_config

2. Conclusion

  • Swift + Container View（In IB）
  • Objective-C + AVPlayerLayer (In Code)

3. Definiton

- prepareForSegue:sender:

Notifies the view controller that a segue is about to be performed.

###Discussion

The default implementation of this method does nothing. Your view controller overrides this method when it needs to pass relevant data to the new view controller. The segue object describes the transition and includes references to both view controllers involved in the segue.

Because segues can be triggered from multiple sources, you can use the information in the segue and sender parameters to disambiguate between different logical paths in your app. For example, if the segue originated from a table view, the sender parameter would identify the table view cell that the user tapped. You could use that information to set the data on the destination view controller.