Skip to content
This repository has been archived by the owner on Aug 7, 2020. It is now read-only.
/ RFSegue Public archive
forked from RFUI/RFSegue

Missing features for UIStoryboardSegue

License

Notifications You must be signed in to change notification settings

Chinamobo/RFSegue

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

39 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

RFSegue - Missing features for UIStoryboardSegue

*English* [简体中文](Readme~zh-hans.md)

Source & Destination Delegate

By default, only UIViewController's prepareForSegue: can notify us the segue will perform. But We can't know when the segue performed. At the same time, you can't stop a segue to be preformed on iOS5.

So we provide RFSegueSourceDelegate and RFSegueDestinationDelegate. You can decide wether should perform a segue or not. Get notify when a segue will perform and did perform.

Tips: After iOS6, you can use shouldPerformSegueWithIdentifier:sender: instead of RFSegueShouldPerform:.

Return buttons

Using segue we can transit between view controllers conveniently from the outside in. But how to return? Generally we must write some code. We had subclassed UIButton and UIBarButtonItem to make this as convenient as segue. For an UIButton, you just change it’c class, no more operate! You need drag masterViewController IBOutlet to current view controller if there are UIBarButtonItem. IBAction or addTarget no longer needed.

Also, RFSegueReturnDelegate provide necessary notifications and control.

Packages

No packages published

Languages

  • Objective-C 100.0%