> On Oct 10, 2015, at 14:50, Alex Hall <[email protected]> wrote:
> 
> 
>> On Oct 10, 2015, at 14:23, Quincey Morris 
>> <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> On Oct 10, 2015, at 05:43 , Alex Hall <[email protected] 
>> <mailto:[email protected]>> 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 protected] 
>> <mailto:[email protected]>> 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.

I just tried it. I erased my segue, and made a new one, this time being sure to 
choose "selection" from the menu. This doesn't seem to have changed anything. I 
added some print statements to my prepareForSegue method, and they aren't 
running, so the segue is definitely not being triggered.
>> 
>> 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 protected] <mailto:[email protected]>


--
Have a great day,
Alex Hall
[email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to