Oops, forgot my question:
How can I work around this problem? I need to install the popover button item,
but I don't have it.
I tried setting the delegate in IB, given that it's all visible in the
storyboard, but it won't let me set the split view delegate across scenes.
---
It seems that whe
It seems that when using storyboards, UISplitViewController gets loaded and
calls its delegate before the related view controllers even get loaded. I'm
trying to set my right-side view controller as the delegate in its
-viewDidLoad, but at this point it's too late, and the willHide delegate meth
On Nov 15, 2012, at 3:17 PM, Graham Cox wrote:
> How can I invoke a method of my protocol on the main thread?
Aside from Greg's simple suggestion, GCD is your friend. Then you're not
beholden to a single method call, or the interface requirements of the
performSelector methods.
dispatch_async(
On Nov 15, 2012, at 17:55 , Kyle Sluder wrote:
> In particular, I'm concerned about -updateTrackingAreas. This message is
> sent to the view, not the tracking area's owner, but the view itself
> doesn't know about the tracking area. If the owner doesn't happen to be
> a view in the same hierarchy
I just put together a quick sample project to prove to myself that one
can safely install a tracking area on a subview:
http://www.optshiftk.com/wp-content/uploads/2012/11/SubviewTrackingArea.zip
But I'm still not convinced that this is guaranteed to work. It doesn't
help that using Google I canno
On Nov 15, 2012, at 17:04 , Kyle Sluder wrote:
> Override -didChangeValueForKey:?
Apparently we are strongly discouraged from overriding those methods. :-)
--
Rick
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin
On Nov 15, 2012, at 4:19 PM, Rick Mann wrote:
> I know I can use KVO on a specific property of my NSManagedObject, but is
> there a way to get notified if any property changes? I'm trying to avoid a
> bunch of -addObserver:… and -removeObserer:… calls.
>
> I know I can listen for the context d
On Nov 15, 2012, at 16:32 , Sean McBride wrote:
> On Thu, 15 Nov 2012 16:19:53 -0800, Rick Mann said:
>
>> I know I can use KVO on a specific property of my NSManagedObject, but
>> is there a way to get notified if any property changes? I'm trying to
>> avoid a bunch of -addObserver:… and -remo
On Thu, 15 Nov 2012 16:19:53 -0800, Rick Mann said:
>I know I can use KVO on a specific property of my NSManagedObject, but
>is there a way to get notified if any property changes? I'm trying to
>avoid a bunch of -addObserver:… and -removeObserer:… calls.
You could create a dependent key, that de
On Nov 15, 2012, at 16:19 , Rick Mann wrote:
> I know I can use KVO on a specific property of my NSManagedObject, but is
> there a way to get notified if any property changes? I'm trying to avoid a
> bunch of -addObserver:… and -removeObserer:… calls.
>
> I know I can listen for the context d
I know I can use KVO on a specific property of my NSManagedObject, but is there
a way to get notified if any property changes? I'm trying to avoid a bunch of
-addObserver:… and -removeObserer:… calls.
I know I can listen for the context did save notification, but I'd rather catch
the changes im
I have a view controller in a storyboard with a static content grouped-style
table. One of the sections has seven table view cells, all built in "right
detail" type.
I have IBOutlet UILabel* references to each of the right-hand detail labels,
and those get updated in my view controller. However
On 16/11/2012, at 10:23 AM, Greg Parker wrote:
> The simple solution is to declare your property as NSObject* .
>
D'oh!!
Thanks - that was simple. I thought I'd tried it, but my syntax was wrong: I
had NSObject*
--Graham
___
Cocoa-dev mailing
On Nov 15, 2012, at 3:17 PM, Graham Cox wrote:
> I have a formal protocol for a notification callback I want to make. The
> protocol inherits the NSObject protocol.
>
> The caller accepts only objects conforming to this protocol as its delegate.
> When it's time to invoke the callback, I'd like
Hi all,
I have a formal protocol for a notification callback I want to make. The
protocol inherits the NSObject protocol.
The caller accepts only objects conforming to this protocol as its delegate.
When it's time to invoke the callback, I'd like to do so on the main thread,
since the caller
I've got this behavior in both the sim and on device that, after a fresh
install of my app, upon launch it presents the alert requesting permission for
location services, which then immediately disappears. I tried googling for a
solution, but can't come up with suitable search terms that don't j
On Nov 14, 2012, at 4:48 PM, Jerry Krinock wrote:
> Now, my app itself does not handle the URL directly. The URL handler is
> actually installed in a faceless helper app which is in the main app's
> Contents/Helpers/ directory. (This was done so I could control whether or
> not my app is ac
On Nov 15, 2012, at 4:59 AM, William Squires wrote:
> @interface Thing : NSObject
>
> @property (nonatomic, ???) Thing *nextThing;
> @property (nonatomic, ???) Thing *prevThing;
>
> @end
>
> and somewhere I keep a reference to the 'head' of this doubly-linked list.
> What should ??? be, "retai
On 15 Nov, 2012, at 12:47 PM, Daniel DeCovnick wrote:
> Strong/retain for next, weak/assign for previous.
> On Nov 14, 2012, at 7:59 PM, William Squires wrote:
>
>>
>> @interface DoublyLinkedListClass
>>
>> @property (nonatomic, retain) Thing *head;
>>
>> @end
>>
>> "doublist.m"
>> @implem
On 14 Nov 2012, at 22:10, Graham Cox wrote:
>
> On 15/11/2012, at 8:59 AM, Nick Zitzmann wrote:
>
>> Oh. I understand how that could happen with GC if the app tried to re-use a
>> finalized object, but the only resurrections I've seen happen under RR or
>> ARC were zombies… Sorry.
>
>
> W
20 matches
Mail list logo
