One more update. I tried connecting my outlet, not to the table inside my view, 
but to the table in the clip view in the table in the view… If that makes 
sense. :) It suddenly started working, and now I have a table with two rows, 
just as my model specifies. The only problem is that these rows are showing 
text of "Table View Cell", rather than the text I want. Clearly, I'm missing 
something important about making custom cells (this is a view-based table, not 
a cell-based table, by the way). Still, we're getting there, i think.
> On Aug 29, 2015, at 7:43 PM, Alex Hall <[email protected]> wrote:
> 
> Thanks, see below.
>> On Aug 29, 2015, at 7:35 PM, Yuma Decaux <[email protected]> wrote:
>> 
>> Hi Alex,
>> 
>> Just to clarify, can you answer thee following:
>> 1-are you using a custom NStableCell to populate your NSTableView, and how 
>> are you calling NSTableViewCell through your delegate protocol?
> I'm creating the cell in my table delegate, but honestly I'm not clear on the 
> process. I know I should create a cell somewhere and set it up how I want 
> each row to look, but just how to do that is where I'm not following the 
> (visual) instructions I've found online. Right now, my tableView method in 
> the delegate/data source class just generates a new cell and returns it, 
> having set its stringValue attribute to the corresponding item in the model's 
> array. I have no idea if that'll actually work or not.
> 
>> 2-Are you using a subclass of NSTableView or are you using the .nib 
>> reference for your custom cell?
> I just put an NSTableView object from the library into my view, like normal. 
> In it I see a clip view, two scrollers, and a table header view. The clip 
> view appears to hold my actual table, which is quite confusing as no 
> instructions online mention this clip view at all, let alone that it holds 
> the actual table.
> 
>> 
>> This might help me understand better the issue.
>> 
>> Cheers,
>> 
>> 
>> 
>>> On 30/08/2015, at 9:30 AM, Alex Hall <[email protected]> wrote:
>>> 
>>> Quick update. I changed the class of my outlet to NSScrollView, and things 
>>> connected straight away. I changed it back to NSTableView, and the 
>>> connection persisted. I'm now seeing a blank window (save the usual Close 
>>> and Minimize buttons) in my app, with no sign of the text field and table 
>>> I've added. I have no clue why my connection suddenly worked, or why 
>>> nothing is showing. In future, should I connect to something other than the 
>>> table view in the outline? Perhaps the table inside the clip view?
>>>> On Aug 29, 2015, at 6:11 PM, Alex Hall <[email protected]> wrote:
>>>> 
>>>> Hi all,
>>>> Sorry to post this here, but it's the only place I know of where a few 
>>>> blind Xcode users might see it. Please respond off-list to 
>>>> [email protected]. Thanks.
>>>> 
>>>> I'm using Xcode 7 beta 6, and I have a table in a Mac app. The table was 
>>>> connected to an IBOutlet and showed as "connected in the ruler, then I was 
>>>> trying to put a cell in it to use as a data source view and it wasn't 
>>>> working. I eventually tried moving the table to the cell, rather than the 
>>>> cell to the table, and that's when my connection broke.
>>>> 
>>>> I have since tried re-connecting it several times, and have even deleted 
>>>> the table and added a new one. Nothing, though, seems to work. I have no 
>>>> idea why, as the process I'm using has worked consistently for months. 
>>>> Strangely, when I run the app, it runs, but focus never switches to it. If 
>>>> I command-tab to it, VoiceOver says the app's name, but I still seem to be 
>>>> in Xcode. Before, I could see an empty table, just as I'd expect, along 
>>>> with the other buttons and such in my app.  None of this craziness 
>>>> happened until after the connection broke, and the only warnings I see are 
>>>> for some layout ambiguities. If anyone can suggest what I am doing wrong, 
>>>> or how to fix this perplexing problem, I'd be very grateful. Thanks in 
>>>> advance.
>>>> 
>>>> --
>>>> Have a great day,
>>>> Alex Hall
>>>> [email protected]
>>>> 
>>> 
>>> 
>>> --
>>> Have a great day,
>>> Alex Hall
>>> [email protected]
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "MacVisionaries" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/macvisionaries.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "MacVisionaries" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/macvisionaries.
>> For more options, visit https://groups.google.com/d/optout.
> 
> 
> --
> Have a great day,
> Alex Hall
> [email protected]
> 


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

-- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

Reply via email to