Re: objc [66375] class Foo is implemented in both BundleA and BundleB

> On May 11, 2016, at 5:11 PM, Jeff Szuhay wrote: >> On May 11, 2016, at 12:08 AM, Jens Alfke wrote: >>> On May 10, 2016, at 11:05 PM, Jeff Szuhay >> > wrote: >>> >>> Class Foo is a base class. It is subclassed in BundleA, BundleB, … BundleZ. >> >> Where is Foo itself

Application Activation Problem

Hi All, I’m using: [myRunningApp activateWithOptions:(NSApplicationActivateAllWindows | NSApplicationActivateIgnoringOtherApps)]; To activate an Application. Is there any way to tell when the Application is actually active? I have the need to cycle through an Array of App Bundle IDs and make

Re: ARC [was Protecting against "app nap"]

Hi, The other thing to watch out for is if you have non ARC Classes in your project, you can forget that they are using assign rather than weak for properties (so the reference doesn’t get zeroed) that can lead to sending message to objects that have been destroyed if you are not careful. You h

Re: Application Activation Problem

On Fri, May 13, 2016, at 04:46 AM, Dave wrote: > Hi All, > > I’m using: > > [myRunningApp activateWithOptions:(NSApplicationActivateAllWindows | > NSApplicationActivateIgnoringOtherApps)]; > > To activate an Application. Is there any way to tell when the Application > is actually active? I have

Re: objc [66375] class Foo is implemented in both BundleA and BundleB

On Fri, May 13, 2016, at 03:23 AM, Jeff Szuhay wrote: > > > On May 11, 2016, at 5:11 PM, Jeff Szuhay wrote: > >> On May 11, 2016, at 12:08 AM, Jens Alfke wrote: > >>> On May 10, 2016, at 11:05 PM, Jeff Szuhay >>> > wrote: > >>> > >>> Class Foo is a base class. It is sub

Re: unwind segue on navigation pop

On Thu, May 12, 2016, at 09:48 PM, Roland King wrote: > I’m making more use of unwind segues to try and get to the point I have > ‘go forward’ and ‘go backward’ code in one place in the same class. So > during prepareForSegue I set some stuff up, during my unwind segue method > I tear it down again

Re: Application Activation Problem

Hi, > You might consider subscribing to > NSWorkspaceDidActivateApplicationNotification and cycling to the next > app in the list upon receipt, but the best you can do is best-effort. > > --Kyle > That’s actually what I am doing. I monitor NSWorkspaceApplicationWllLaunchNotification, NSWorksp

Re: Application Activation Problem

On Fri, May 13, 2016, at 10:21 AM, Dave wrote: > Hi, > > > You might consider subscribing to > > NSWorkspaceDidActivateApplicationNotification and cycling to the next > > app in the list upon receipt, but the best you can do is best-effort. > > > > --Kyle > > > > That’s actually what I am doing

Re: objc [66375] class Foo is implemented in both BundleA and BundleB

> On May 13, 2016, at 1:23 AM, Jeff Szuhay wrote: > > 1) Project headers are only available within the framework and not to any > other “consumer” of the framework. >Which is to say, my bundles, which “consume" the framework, cannot see > project headers. Right. “Project” is just the defa

Recurrent background thread

I want a method running on a background thread to reissue itself after it is done processing. How can I do this? I'm using the following code but it runs just once and is never heard from again... // initial invocation from main thread [self performSelectorInBackground:@selector(_checkS

Re: Recurrent background thread

I’ve had luck using dispatch queues to accomplish recurring events, specifically dispatch_after. For example: - (void) doStuffAfterDelay { dispatch_queue_t theQueue = dispatch_queue_create("Recurring work queue", DISPATCH_QUEUE_SERIAL); dispatch_time_t futureTime = dispatch_time(DISPATCH_

Re: Recurrent background thread

Thanks! I knew I was doing it the /old/ way! -Carl > On May 13, 2016, at 12:56 PM, Doug Hill wrote: > > I’ve had luck using dispatch queues to accomplish recurring events, > specifically dispatch_after. For example: > > - (void) doStuffAfterDelay > { >dispatch_queue_t theQueue = dispatch_

Re: Recurrent background thread

> On May 13, 2016, at 12:34 PM, Carl Hoefs > wrote: > > As a test, the above works if run on the main thread, so I'm guessing it has > something to do with there being no runloop after the background thread > exits. Yup. More precisely, the background thread has no runloop at all. Its top-l

Re: ARC [was Protecting against "app nap"]

If that wasn’t called out clearly in that non-ARC class’s documentation/header, then that non-ARC class was Doing It Wrong(tm). > On May 13, 2016, at 2:55 AM, Dave wrote: > > Hi, > > The other thing to watch out for is if you have non ARC Classes in your > project, you can forget that they a

Re: unwind segue on navigation pop

> On 13 May 2016, at 23:03, Kyle Sluder wrote: > > On Thu, May 12, 2016, at 09:48 PM, Roland King wrote: >> I’m making more use of unwind segues to try and get to the point I have >> ‘go forward’ and ‘go backward’ code in one place in the same class. So >> during prepareForSegue I set some stuff