GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Help/Help/UIKit/UnwindSegue.swift at master · lgreydev/Help

Expand file tree

/

UnwindSegue.swift

Copy path
More file actions
More file actions

Latest commit

 

History

History
History
26 lines (20 loc) · 1.42 KB
/

UnwindSegue.swift

Copy path

File metadata and controls

26 lines (20 loc) · 1.42 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
//
// UnwindSegue.swift
// Help
//
// Created by Sergey Lukaschuk on 07.06.2021.
//
import Foundation
// MARK: - Unwind Segue
/// Article https://developer.apple.com/documentation/uikit/resource_management/dismissing_a_view_controller_with_an_unwind_segue
/// Dismissing a View Controller with an Unwind Segue
/// Configure an unwind segue in your storyboard file that dynamically chooses the most appropriate view controller to display next.
/// To handle the dismissal of a view controller, create an unwind segue.
/// Unlike the segues that you use to present view controllers, an unwind segue promises the dismissal of the current view controller without promising a specific target for the resulting transition. Instead, UIKit determines the target of an unwind segue programmatically at runtime.
/// UIKit determines the target of an unwind segue at runtime, so you aren’t restricted in how you set up your view controller hierarchies.
/// Consider a scenario where two view controllers present the same child view controller, as shown in the following figure. You could add complicated logic to determine which view controller to display next, but such a solution wouldn’t scale well. Instead, UIKit provides a simple programmatic solution that scales to any number of view controllers with minimal effort.
/*
@IBAction func myUnwindAction(unwindSegue: UIStoryboardSegue) {
// Connect a Triggering Object to the Exit Control
}
*/
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.