Did you mean INappropriate?
Sent from my iPhone
On Aug 31, 2012, at 21:11, Scott Anguish wrote:
> This has gone far enough.
>
> The thread is closed. It is appropriate for this list.
>
>
> On Aug 31, 2012, at 5:29 PM, Jeffrey Oleander wrote:
>
>>> From: davel...@mac.com
>>> To: cocoa-dev@
Angry Birds does it so it must be possible. So how can I do this as well? I
need my app to truly take over the entire iPhone screen with no distractions
and no dangerous hit area that can take the user out of my app by accident.
Thanks
___
Cocoa-dev
I've got a simple app that uses a navigation controller and a series of
UIWebViews to handle the UI. When I want to load a new view controller that
just has a web view as the entire view, allocate it, init it with the request
it is supposed to display, and then push it onto the navigation contr
t;
> Am 01.03.2010 um 08:12 schrieb Eagle Offshore:
>
>> NSManagedObject* obj; // gets created somehow
>>
>> [obj setValue: nil forKey: @"bar"]; // succeeds where NSDictionary fails
>> [obj setValue: [NSNull null] forKey: @"bar"]; // fails where NSDict
All my audio render callbacks use the C-function-pointer-to-call-named-selector
trick in JambaLaya. (http://audiofreakshow.com)
In fact, the entire app is written in Objective-C. Between SnoizeMIDI,
MTCoreAudio, and my own private TBAudioUnits framework - I deal with C or C++
almost never.
@"bar"]; // fails where NSDictionary
succeeds
so - this is conceptually buggy thinking and the thoughtful developer could be
forgiven for being VERY SURPRISED by this behavior that is NOT DOCUMENTED.
On Feb 28, 2010, at 6:31 PM, Kyle Sluder wrote:
> On Sun, Feb 28, 2010 at 6:16 PM, Ea
Unacceptable type of value for attribute: property = "notes";
desired type = NSString; given type = NSNull; value =
Really? This is a problem somehow?
NSManagedObject couldn't just take the hint and go with nil?
-Todd Blanchard
___
Cocoa-dev mai
I thought I'd share the underlying cause. In prior versions of OS X,
if the contents of the file was nil, NSFileWrapper would just create
an empty file. No problem. Empty file.
Under Snow Leopard, NSFileWrapper writing aborts cryptically if any of
the files' contents are nil or the wrapp
See other message - it makes zero difference.
On Oct 13, 2009, at 9:21 PM, Graham Cox wrote:
On 14/10/2009, at 3:07 PM, Eagle Offshore wrote:
I'm compiling against 10.4 SDK. I started this project under
Tiger. Its the same project file.
On Oct 8, 2009, at 2:07 AM, Gabriel Zachmann
K, I've reduced the method to
- (NSFileWrapper *)fileWrapperOfType:(NSString *)aType error:
(NSError**)errPtr
{
NSFileWrapper* wrapper = [[NSFileWrapper alloc]
initDirectoryWithFileWrappers:nil];
return [wrapper autorelease];
}
and it still produces the same error with no explanati
I'm compiling against 10.4 SDK. I started this project under Tiger.
Its the same project file.
On Oct 8, 2009, at 2:07 AM, Gabriel Zachmann wrote:
And it is maddening because the error occurs outside my code. My
document class implements
Maybe I missed it, but ... are you compiling with
d, and only now it has
a problem in Snow Leopard and the problem seems to be deep in
framework code. A console log message giving a clue to the cause of
the error would not be out of line, Apple.
On Oct 6, 2009, at 5:47 PM, Graham Cox wrote:
On 07/10/2009, at 11:23 AM, Eagle Offshor
And it is maddening because the error occurs outside my code. My
document class implements
- (NSFileWrapper *)fileWrapperOfType:(NSString *)aType error:
(NSError**)errPtr
and this gets called fine. It returns a new NSFileWrapper. It has
been working perfectly since Tiger (this app targe
If I'm doing a lot of swapping of a limited number of views, I stick
them in a tabbed view with hidden tabs.
On Jul 5, 2009, at 3:18 PM, Pierce Freeman wrote:
Hi Everyone:
I am making an application that has a choice of what function the
user wants
to perform. When the user clicks on thei
14 matches
Mail list logo
