Hi,
On 11/12/2017 20:10, Quincey Morris wrote:
I made my own text field class according to this (in NSTableCellView's doc) :
I think you’re still kinda Doing It Wrong™. The standard (and, I believe,
recommended) way to do this is to create an instance of
NSTableCellView, which has the “object
Hi Richard,
thanks for all this reading !
I'll need a day or two to understand everything therein. Even if they aren't
that long, there are a lot of subtle details :)
Too bad that bindings are fading away, the concept is great, the implementation
is not so great from skimming thru these pages.
I have configured Background Fetch at the "Capabilities" tab in my
Project's settings. Then added to the App delegate:
-(void)application:(UIApplication *)application
performFetchWithCompletionHandler:(void
(^)(UIBackgroundFetchResult))completionHandler
{
NSLog(@"### Received Back
On Dec 12, 2017, at 02:12 , Eric Matecki wrote:
>
> In the case of NSTableCellView, neither binding works... I don't get any
> exception or crash, but nothing is displayed inside my table view (although
> it's size suggests the four rows are there).
This was a conceptual failure on my part, si
> On Dec 12, 2017, at 12:08 PM, Quincey Morris
> wrote:
>
> I don’t think bindings are fading away. They can’t, while they’re the only
> way to connect UI elements without custom glue code. However, the design is
> ancient (IIRC, bindings were introduced in macOS 10.3, and refined in 10.4,
>
Did you confirm that there is a UIBackgroundModes key in your app's Info.plist?
UIBackgroundModes
fetch
> On Dec 12, 2017, at 6:23 AM, Viacheslav Karamov wrote:
>
> I have configured Background Fetch at the "Capabilities" tab in my Project's
> settings. Then added to the App delega
> On 12 Dec 2017, at 19:56, Richard Charles wrote:
>
> I always assumed the reason bindings never came over to iOS was they consumed
> too much cpu power and were too difficult to understand. It seems evident
> that 10 or 20 years from now Apple anticipates the bulk of it programmers
> coming
> On Dec 12, 2017, at 2:40 PM, Jonathan Mitchell wrote:
>
>> On 12 Dec 2017, at 19:56, Richard Charles wrote:
>>
>> I always assumed the reason bindings never came over to iOS was they
>> consumed too much cpu power and were too difficult to understand. It seems
>> evident that 10 or 20 year
When using the absolutePathForApplication(withBundleIdentifier:) api, I find
that if the path is on an external mount, the api will return nil / none if the
uid is 0, when it will return an actual path when the uid is a valid user login
id (eg, 501, 502 etc).
To reproduce, mount a .dmg contain
