That is mostly right.
if you have more than one column, you select one of the table column objects in
the outline and set it’s identifier in the identity inspector. If you only
have one column, you can just use the automatic one.
Also, you can set an identifier for the cell to access it from the
Thanks. So as long as I have only one instance of NewCell (or whatever I call
it) in the storyboard, Xcode will automatically find it, right? Is the
column.identifier important? Well, I know it's important, but how does the
string it contains relate to the type of cell? I'll have a guess: the cl
Nstty,
I think Alex was wondering where the identifier for the column is set which
appears to be a string So if column 2 is identified as "Expenses" how does one
associate the column with the identifier of "Expenses", so it can be used in
the code he pprovided.
.
Jonathan Cohn
> On Aug 30,
If you are using a custom class, you set the class of the tableCellView in IB
in the identity inspector. To find it in the outline, expand the tableview and
then the table column.
After you design the cellView by adding elements and laying them out, you will
need to connect them to outlets in y
It can be, or you can use one of the pre-configured cells Apple provides. The
part I'm stuck on is how to tell Xcode that the cell I made--subclass or
default--is the one I want it to use to populate my table. There's a method for
it, and clearly I'm supposed to give it a string (as column.ident
Would it just be a subclass?
Jonathan Cohn
> On Aug 29, 2015, at 8:43 PM, Alex Hall wrote:
>
> Don't ask me how, but I think I have it working. My raining question is: how
> do you create, then use, a custom cell view? I'm using the default one now,
> which is just a text field, and that's
Don't ask me how, but I think I have it working. My raining question is: how do
you create, then use, a custom cell view? I'm using the default one now, which
is just a text field, and that's all I need for the moment. In general, though,
how would I go about making a custom cell view and then u
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 a
Thanks, see below.
> On Aug 29, 2015, at 7:35 PM, Yuma Decaux 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 c
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?
2-Are you using a subclass of NSTableView or are you using the .nib reference
for your custom cell?
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 a
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 mehg...@icloud.com. 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
12 matches
Mail list logo
