ios - A duplicated segue processing with UIStoryBoardSegue between two UIViewControllers -

-

this question has answer here:

i have 2 screens. first based on uitableview instance. when tap cell, function tableview(_:didselectrowat:) triggers:

func tableview(_ tableview: uitableview, didselectrowat indexpath: indexpath) {         selectedemg = selectedemergencies[indexpath.row]         performsegue(withidentifier: "showmoreinfoaboutemg", sender: self)     }

here storyboard:

storyboard

but in fact, segue "showmoreinfoaboutemg" duplicates , second screen.

enter image description here

i can cut performsegue(withidentifier:sender:) , transition between screens work correctly. need transfer data uitableviewcell instance remote uiviewcontroller's property. otherwise this:

enter image description here

prepare(for:sender:) starts work earlier tableview(_:didselectrowat:) , remote view controller gets nil object cell. tips, guys?

the decision found.

the simple , useful uitableview's property indexpathforselectedrow.

i didn't touch storyboard removed tableview(_:didselectrowat:) implementation , have added 1 line. it's enough use prepare(for:sender:) totally. general implementation below:

override func prepare(for segue: uistoryboardsegue, sender: any?) {         if segue.identifier == "somecustomidentifier" {             guard let remoteviewcontroller = segue.destination as? customviewcontroller else {                 fatalerror("customviewcontroller instance not found 👎🏻")             }             selecteditem = items[(self.customtableview.indexpathforselectedrow?.row)!]             remoteviewcontroller.selecteditemfromtable = selecteditem         } }

maybe simpler:

func tableview(_ tableview: uitableview, didselectrowat indexpath: indexpath) {     let selectedemg = selectedemergencies[indexpath.row]     if let vc = storyboard?.instantiateviewcontroller(withidentifier: "emgdetailspresenter") as? emgdetailspresenter {         vc.selectedemgfromtable = selectedemg         navigationcontroller?.pushviewcontroller(vc, animated: true)     } }

p.s. don't forget remove segue in storyboard , add storyboard id emgdetailspresenter


Comments

Post a Comment

Popular posts from this blog

ios - MKAnnotationView layer is not of expected type: MKLayer -

-
Image
so code works fine logger riddled message. there way rid of or suppress it? postannotation.swift class postannotation: mkpointannotation { //mark: properties let post: post //mark: initialization init(post: post) { self.post = post super.init() self.coordinate = cllocationcoordinate2d(latitude: post.latitude, longitude: post.longitude) self.title = post.title self.subtitle = post.timestring() } } adding annotation let annotation = postannotation(post: post) self.map.addannotation(annotation) func mapview func mapview(_ mapview: mkmapview, viewfor annotation: mkannotation) -> mkannotationview? { if annotation mkuserlocation { return nil } var annotationview = mapview.dequeuereusableannotationview(withidentifier: "pin") as? mkpinannotationview if annotationview == nil { annotationview = mkpinannotationview(annotation: annotation, reuseidentifier: "pin")
Read more

ZeroMQ on Windows, with Qt Creator -

-
i have installed zmq link given below on windows 7. http://zeromq.org/distro:microsoft-windows 1) have c++ project in qt-creator , i'm using zmq c++ binding (zhelpers.hpp etc). 2) have added .lib installed zmq folder qtcreator 3) while compiling, compiler looks _imp__zmq_verion, in .dll files present in .lib have __imp_zmq_version. 4) causing undefined reference zmq_version. anyone else faced problem , has solution ?
Read more

unity3d - Unity SceneManager.LoadScene quits application -

-
i have 2 different scenes 1 named 'main' , other 'game' both added scenes in load. when use scenemanager.loadscene("game"); works no problem when tried return main scene code if (input.getkeydown (keycode.escape)) { scenemanager.loadscene("main"); } strangely game quits. thanks. sorry interruption. somewhere on other script found code. if (input.getkeydown (keycode.escape)) { application.quit (); } that's bad, know...
Read more