ios - Firing a segue from a different view -


i have segue navigates firstviewcontroller secondviewcontroller. happens press of button. code button is

- (ibaction)segue:(id)sender { [self performseguewithidentifier:@"myidentifier" sender:self]; }

this happens correctly when press button.

what trying fire method view. tried doing

firstviewcontroller fvc = [[firstviewcontroller alloc] init]; [fvc segue:nil];

when try this, error message, reciever has no segue identifier 'myidentifier'

how fire segue programatically view?

there few issues here, boil down couple of key points:

  • segues storyboard thing, view controllers "know" segues if they're instantiated storyboard.
  • a view controller must onscreen perform segue.
  • segues transitions 1 specific view controller specific view controller.

so, in snippet:

firstviewcontroller fvc = [[firstviewcontroller alloc] init]; [fvc segue:nil];

the first problem alloc-init-ing gives instance of firstviewcontroller doesn't know storyboard came from, doesn't know segues. (this alone fixed using [instantiateviewcontrollerwithidentifier:][1], doesn't solve whole problem.) second problem instance doesn't fit anywhere ui hierarchy -- hasn't been presented modal view controller, it's not top view controller in current navigation controller, it's not visible window's root view controller, etc. in order transition screen 1 view another, first view needs onscreen.

what sounds want transition what's onscreen target of segue. notion of storyboard segue isn't transition destination -- it's source, destination, , transition or relationship between them. if have different source view, need different segue. so, if have segue firstviewcontroller secondviewcontroller, , want make similar transition otherviewcontroller (assuming that's 1 onscreen now) secondviewcontroller, need make second segue connecting otherviewcontroller secondviewcontroller.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more