> On 18 Jul 2015, at 14:37, Nick wrote:
>
>
> here. Could you suggest me what am i doing wrong?
> Thanks
>
>
> if([[tableColumn identifier] isEqualToString:@"FirstColumn"]) {
>
> NSTableCellView *tableCellView = [tableView makeViewWithIdentifier:
> @"FirstColumnCellView" owner:tableV
On or about 2/7/10 9:46 AM, thus spake "MARC BLATT" :
> Thanks to all. Not one of my better days. Forgot to save. :(
It used to be that when you had unsaved changes IB, Xcode would propose to
save for you when you built the project. But this feature has been missing
for a while, and I regard its
Thanks to all. Not one of my better days. Forgot to save. :(
On Feb 7, 2010, at 5:27 AM, Alastair Houghton wrote:
> On 6 Feb 2010, at 00:44, MARC BLATT wrote:
>
>> I have the following code in viewWillAppear: for my iPhone dev project
>> (iPhone Development SDK Book, Chapter 4, p.63):
>
> [sni
Thanks to all. Not one of my better days. Forgot to save. :(
On Feb 7, 2010, at 9:05 AM, Matt Neuburg wrote:
> On Fri, 5 Feb 2010 16:44:40 -0800, MARC BLATT said:
>> self.summaryLabel.text = self.movie.summary;
>> NSLog(@"%@ sold %@ because %@", self.movie.title,
> [formatter stringFromNumber:sel
On Fri, 5 Feb 2010 16:44:40 -0800, MARC BLATT said:
> self.summaryLabel.text = self.movie.summary;
> NSLog(@"%@ sold %@ because %@", self.movie.title,
[formatter stringFromNumber:self.movie.boxOfficeGross], self.movie.summary);
> NSLog(@"%@ sold %@ because %@", self.titleLabel.text,
self.boxOffice
On 6 Feb 2010, at 00:44, MARC BLATT wrote:
> I have the following code in viewWillAppear: for my iPhone dev project
> (iPhone Development SDK Book, Chapter 4, p.63):
[snip]
> NSLog(@"%@ sold %@ because %@", self.movie.title, [formatter
> stringFromNumber:self.movie.boxOfficeGross], se
On Jan 6, 2009, at 10:44, WT wrote:
It just occurred to me, though, that the KVO mechanism *could* do
something special for dependent keys, namely, pass the original
change dictionary on to the observer of the dependent key. After
all, it does know that it's dealing with a dependent key. As
It just occurred to me, though, that the KVO mechanism *could* do
something special for dependent keys, namely, pass the original change
dictionary on to the observer of the dependent key. After all, it does
know that it's dealing with a dependent key. As it is, once I get the
notification
Hi Quincey,
thank you for your reply.
In this scenario, typically the dependent property doesn't have a
useful value -- all you care about is the notification.
Yes, that's my intention.
If you *are* trying to maintain a genuine value for the
"displayNeeded" property, then we need to see t
On Jan 6, 2009, at 06:55, WT wrote:
The reason for the comparison between the old and new values should
be obvious, namely, I don't want to redraw the screen unless the
value of the original key has in fact changed.
Now, here's the problem: when I run my app, both the old and new
values a
10 matches
Mail list logo
