• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Basic question on connecting table view to prototype cells
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Basic question on connecting table view to prototype cells


  • Subject: Re: Basic question on connecting table view to prototype cells
  • From: Alex Hall <email@hidden>
  • Date: Sat, 10 Oct 2015 14:50:03 -0400


On Oct 10, 2015, at 14:23, Quincey Morris <email@hidden> wrote:

On Oct 10, 2015, at 05:43 , Alex Hall <email@hidden> wrote:

When I make a segue from, say, a button to a scene, I drag from the scene's connections inspector to the button that will launch the segue, so I figured I should do the same thing here--from the scene to the cell.

Ah, OK. When you’re using the inspection connection buttons (to avoid control-dragging on the canvas), it doesn’t matter whether you drag from the source to the destination or the destination to the source. Either way, it’s still a segue from the cell to the detail view.

Good to know, thanks. I have to do it this way, since VoiceOver doesn't support control-dragging. Technically it does, but not for how Xcode is set up.

On Oct 9, 2015, at 21:36 , Alex Hall <email@hidden> wrote:

I have a UITableView displaying rows of data, which is good, but tapping on a row does nothing, which is the problem.

When you create the segue as above, you get that popup menu we discussed recently. In this case, it has two choices: selection, and accessory action. Are you sure you chose the right one (selection)?

No tutorial ever mentioned which to choose, so I've tried both. I'll give the selection one another shot and see if any other changes I've made since might make it work.

Also, it’s not clear what the correct segue type ought to be in your case. You said nothing about navigation controllers or split controllers, so your master/detail relationship is informal, not the one built into iOS, I think.

I tried a navigation controller, but it made its own scene. I have no idea how to use it; I wanted to get this master/detail thing working before moving to a more advanced topic. Perhaps navigation controllers aren't advanced at all, but from the outline table, it's in no way obvious how to use them. Things online just keep telling me to embed my table or table controller in a navigation controller, then change some aspects of that controller, and that seems to be the end of it. I'll look more into it, but as I said, they seemed more complex so I thought I'd master the basics first.




--
Have a great day,
Alex Hall
email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Basic question on connecting table view to prototype cells
      • From: Alex Hall <email@hidden>
References: 
 >Basic question on connecting table view to prototype cells (From: Alex Hall <email@hidden>)
 >Re: Basic question on connecting table view to prototype cells (From: Quincey Morris <email@hidden>)
 >Re: Basic question on connecting table view to prototype cells (From: Alex Hall <email@hidden>)
 >Re: Basic question on connecting table view to prototype cells (From: Quincey Morris <email@hidden>)

  • Prev by Date: Re: Basic question on connecting table view to prototype cells
  • Next by Date: Re: Basic question on connecting table view to prototype cells
  • Previous by thread: Re: Basic question on connecting table view to prototype cells
  • Next by thread: Re: Basic question on connecting table view to prototype cells
  • Index(es):
    • Date
    • Thread