Good point. I guess if the document URL is nil, you should think twice about
this.
On Feb 13, 2014, at 8:38 PM, Kyle Sluder wrote:
> On Thu, Feb 13, 2014, at 05:21 PM, Dave Fernandes wrote:
>> Try returning nil for the document in [NSDocumentController
>> reopenDocumentForURL]’s completion
Kyle,
Yes, AATappableLabel.m is indeed a member of the target. (I checked it multiple
times.) Moreover, I have confirmation of this in other places in the
application, where I use the AATappableLabel class directly embedded in a
UIView (rather than in the contentView of a UITableViewCell) and i
On Thu, Feb 13, 2014, at 05:21 PM, Dave Fernandes wrote:
> Try returning nil for the document in [NSDocumentController
> reopenDocumentForURL]’s completion handler, and also return the
> following error in the completion handler:
>
> [NSError errorWithDomain:NSCocoaErrorDomain code:NSUserCance
Try returning nil for the document in [NSDocumentController
reopenDocumentForURL]’s completion handler, and also return the following
error in the completion handler:
[NSError errorWithDomain:NSCocoaErrorDomain code:NSUserCancelledError
userInfo:nil]
On Feb 13, 2014, at 6:57 PM, Mike Abdul
On Thu, Feb 13, 2014, at 01:53 PM, Rick Aurbach wrote:
> Notice that the storyboard recognizes that the label ought to instantiate
> a custom class (see red text above), but that doesn’t happen
>
> * if I set breakpoints in the initxxx methods, they are never hit
> * if I break in the method
On 13 Feb 2014, at 23:39, Eric Gorr wrote:
>
>
>> On Feb 13, 2014, at 6:22 PM, Mike Abdullah wrote:
>>
>>
>>> On 13 Feb 2014, at 21:12, Eric Gorr wrote:
>>>
>>> What I want to do seems like it should be fairly straightforward, but
>>> doesn't seem to be. All I want to do is with a standa
On Feb 13, 2014, at 3:38 PM, Daniel Wambold wrote:
> Any sensitive information should be encrypted with the 256 bit key, since it
> will be unreadable without the correct password file _as well as_ the correct
> password.
In that case, the file with the password seems unnecessary. You can dir
> On Feb 13, 2014, at 6:22 PM, Mike Abdullah wrote:
>
>
>> On 13 Feb 2014, at 21:12, Eric Gorr wrote:
>>
>> What I want to do seems like it should be fairly straightforward, but
>> doesn't seem to be. All I want to do is with a standard NSDocument Based
>> (with Core Data) is prevent the l
Jens-
You are absolutely correct, and I should have been more clear. The
"authenticated" part is simply so you can provide feedback to the user. ("Your
password was wrong.") Replacing the password file could (assuming you knew the
process) allow one to achieve "authenticated" status, but the dec
On 13 Feb 2014, at 21:12, Eric Gorr wrote:
> What I want to do seems like it should be fairly straightforward, but doesn't
> seem to be. All I want to do is with a standard NSDocument Based (with Core
> Data) is prevent the last document opened from opening automatically the next
> time the a
On Feb 13, 2014, at 2:28 PM, Daniel Wambold wrote:
> I have hacked together a brief sample app illustrating how I prefer to do
> password authentication. It does not use the keychain, which can be useful as
> well. If it's of any interest or use, feel free. It's called
> "MyAuthenticator," wh
Mike-
I have hacked together a brief sample app illustrating how I prefer to do
password authentication. It does not use the keychain, which can be useful as
well. If it's of any interest or use, feel free. It's called "MyAuthenticator,"
which is the first thing listed on the page below. If I un
What I want to do seems like it should be fairly straightforward, but doesn't
seem to be. All I want to do is with a standard NSDocument Based (with Core
Data) is prevent the last document opened from opening automatically the next
time the application is launched.
What is the best way to accom
-[NSPersistentStore metadataForPersistentStoreOfType:URL:error:] failed again
today while testing my app. This time, the stuff it logged to the console was
different than I recall seeing ever before…
CoreData: error: (3850) I/O error for database at /path/to/Document.sql.
SQLite error code:38
This time with the list.
Sent from my iPhone
> On 2014/02/12, at 17:57, John Joyce
> wrote:
>
> So, it was WWDC 2013 session 213 Best Practices for Cocoa Animation
> Some good stuff to get started there.
> That and 2010’s session 214 and 2012’s season 217.
> With those, you should be able to
Hi Rick,
How about putting the barbell image as the contents of a stock CALayer and
use the contentsCenter property to stretch the barbell in the middle
letting CALayer replicating the middle column of pixels as needed?
In this way you should be able to leverage Core Animation fast compositing
and
16 matches
Mail list logo