watchOS

watchOS 3 The watchApp has NotificationController ← WKUserNotificationInterfaceController watchApp gets a Local Notification with one associated UNNotificationAction with title = “Accept” [NotificationController init] [NotificationController didReceiveNotification:withCompletion:]

Re: Representing an object graph

On Dec 5, 2016, at 4:18 PM, Daryle Walker wrote: > I've heard that Core Data is a object graph and persistence library. What if > you want just the first part? The graph seems like a neat way to save on > modeling code, the external format is not database-ish at all (so the

UINavigationBar content margins in UIPresentationController subclass

I have a UIPresentationController subclass with a UINavigationBar embedded in the container view. However, when setting the rightBarButtonItem, the spacing I usually expect from the item to the screen isn't there. http://imgur.com/LHcqhyd Anyone have an idea where I

Why aren't NSFilePromiseProviderDelegate methods being called?

Okay, so I decided to try to experiment with NSFilePromiseProvider, in order to replace some legacy code using old-fashioned drag-and-drop methods. However, for some reason, the drag-and-drop system seems to completely ignore my NSFilePromiseProviderDelegate methods, and calls the old-fashioned

Re: Documentation Workflow

> On Dec 6, 2016, at 3:45 PM, Carl Hoefs wrote: > > Just now I was looking for a list of NSString method signatures to peruse. Open NSString.h? —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do

Re: Using floating point instructions

On Dec 6, 2016, at 4:41 PM, Greg Parker wrote: On Dec 6, 2016, at 7:27 AM, G 3 wrote: I'm working on a program that calls PowerPC assembly floating point instructions from C. It would have calls like this: double inputA, inputB, answer; asm volatile("fadd %0,

Re: Documentation Workflow

> On Dec 3, 2016, at 11:52 AM, Richard Charles wrote: > >> On Dec 2, 2016, at 11:34 AM, Slipp Douglas Thompson >> wrote: >> >> Alternatively, there's always archive.org's Wayback Machine. > >> Since developer.apple.com's URL paths have

Re: iOS 9: Adding CALayer to self.view.layer causes EXC_BAD_ACCESS

> On 2016 Dec 7, at 6:27, Carl Hoefs wrote: > >> >> On Dec 6, 2016, at 1:33 PM, Carl Hoefs >> wrote: >> >>> On Dec 6, 2016, at 1:24 PM, David Duncan wrote: >>> >>> Your safest bets are to either clear

Re: Using floating point instructions

> On Dec 6, 2016, at 7:27 AM, G 3 wrote: > > I'm working on a program that calls PowerPC assembly floating point > instructions from C. It would have calls like this: > > double inputA, inputB, answer; > asm volatile("fadd %0, %1, %2" : "=f" (answer) : "f" (inputA),

Re: iOS 9: Adding CALayer to self.view.layer causes EXC_BAD_ACCESS

> On Dec 6, 2016, at 1:33 PM, Carl Hoefs wrote: > >> On Dec 6, 2016, at 1:24 PM, David Duncan wrote: >> >> Your safest bets are to either clear the delegate of the layer at an >> appropriate time (possibly in your view controller’s

Re: Using floating point instructions

> On 6 Dec 2016, at 15:27, G 3 wrote: > > Is there a way to fix this problem? > Have you tried lowering the release build optimisation level to match the level used for debug build?. It might get you on the right track. J

Re: Drag UITableView up/down

Well, not really. I'll try to explain a bit more. I have a table and it takes up the bottom 1/2 of the screen. When a user swipes up, instead of scrolling the cells, the table moves up the screen until it's at 100px from the top - and at that point, the swipe scrolls the cells up. When the table

Re: iOS 9: Adding CALayer to self.view.layer causes EXC_BAD_ACCESS

> On Dec 6, 2016, at 1:24 PM, David Duncan wrote: > > Your safest bets are to either clear the delegate of the layer at an > appropriate time (possibly in your view controller’s dealloc is all that is > necessary), or to use a UIView instead of a raw CALayer in this

Re: Drag UITableView up/down

It sounds like what you’re really wanting to do is emulate what Apple’s News app is doing, right? First, you set your navigation controller’s hidesBarsOnSwipe to true. The next step is the more difficult one, but it depends on how you want your status bar to appear and if you want a

Re: iOS 9: Adding CALayer to self.view.layer causes EXC_BAD_ACCESS

> On Dec 6, 2016, at 11:51 AM, Doug Hill wrote: > > I've wondered about this before, but maybe some Objective-C runtime experts > know. > > Does writing directly to the ivar backing a property bypass the ARC features > of the property. For example, will a strong property

Re: iOS 9: Adding CALayer to self.view.layer causes EXC_BAD_ACCESS

> On Dec 6, 2016, at 11:44 AM, Carl Hoefs > wrote: > > I get the following crash in my iOS 9 app simply by adding a CALayer to the > current view controller's self.view.layer and then dismissing the current > view controller. Simplified code: > >@property

Re: iOS 9: Adding CALayer to self.view.layer causes EXC_BAD_ACCESS

FWIW, it still crashes if I change the code to use self.layer instead of _layer: @property (strong,nonatomic) CALayer *layer; . . . self.layer = [[CALayer alloc] init]; [self.layer setDelegate: self]; [self.view.layer addSublayer:self.layer]; -Carl > On Dec 6, 2016, at 12:51

Re: iOS 9: Adding CALayer to self.view.layer causes EXC_BAD_ACCESS

I've wondered about this before, but maybe some Objective-C runtime experts know. Does writing directly to the ivar backing a property bypass the ARC features of the property. For example, will a strong property be retained if you write directly to the ivar? If not, that's your problem. Doug

iOS 9: Adding CALayer to self.view.layer causes EXC_BAD_ACCESS

I get the following crash in my iOS 9 app simply by adding a CALayer to the current view controller's self.view.layer and then dismissing the current view controller. Simplified code: @property (strong,nonatomic) CALayer *layer; . . . _layer = [[CALayer alloc] init]; [_layer

Drag UITableView up/down

I'm looking for a chunk of view controller code that allows for: A UITableView. You can drag the whole table up (not the cells) to a limit from the top of the VC, say like 100px. When you've reached that, the table will scroll up normally. When you scroll the table down (cells) and reach item 0,

Re: radio button contrast

> On 05 Dec 2016, at 17:23, J.E. Schotsman wrote: > > Hello, > > I intend to increase contrast of inactive radio buttons a little because they > are hardly legible. > The idea is to draw to a bitmap, increase contrast, draw to screen. > To my surprise this already increases

Re: Large "Data" support

> On Dec 6, 2016, at 12:32 AM, Alastair Houghton > wrote: > > 1. If you mmap() data, you don’t actually have to read all of it; it’s read > from disk on demand. I was assuming Daryle wanted to create the Data from scratch, not read it from a file. If the data

Using floating point instructions

I'm working on a program that calls PowerPC assembly floating point instructions from C. It would have calls like this: double inputA, inputB, answer; asm volatile("fadd %0, %1, %2" : "=f" (answer) : "f" (inputA), "f" (inputB)); // answer = inputA + inputB The odd thing is it only works

Re: Message from iOS to watchOS

That is correct. Local notifications only go to your local device - or the paired device (watch) associated with it. If you want to be able to reach all iOS devices a user has, you would have to use a Remote notification service, and eventually talk to the APNS service. Notifications have

Re: Message from iOS to watchOS

> On 5 Dec 2016, at 21:27, J. Scott Tury wrote: > > Gerriet, > > Try setting a Local Notification to be delivered at a scheduled time in the > future (like a minute later). Then put your iPhone into lock mode, and turn > off the display. > > This should force the OS to

Re: Large "Data" support

On 6 Dec 2016, at 01:15, Jens Alfke wrote: > >> On Dec 5, 2016, at 4:12 PM, Daryle Walker wrote: >> >> For the Swift 3 "Data" type, if I want to represent a multi-gigabyte file, >> it won't try to do it all in memory, would it? > > The Data type