Op 15 jun. 2012, om 14:24 heeft Luca Ciciriello het volgende geschreven:
> I'm porting some CoreImage code from MacOS X to iOS and I'm unable to find
> the key KCGImagePropertyOrientation.
> My doubt is: Is this key available in iOS?
> I'm using iOS 5.1 with Xcode 4.3.3
My documentation serach
Op 15 jun. 2012, om 14:24 heeft Luca Ciciriello het volgende geschreven:
> I'm porting some CoreImage code from MacOS X to iOS and I'm unable to find
> the key KCGImagePropertyOrientation.
> My doubt is: Is this key available in iOS?
> I'm using iOS 5.1 with Xcode 4.3.3
My documentation serach
Yes this is the problem.
Thanks
Luca.
On Jun 15, 2012, at 4:03 PM, Fritz Anderson wrote:
>
> On Fri, June 15, 2012 7:24 am, Luca Ciciriello wrote:
>> Hi All.
>> I'm porting some CoreImage code from MacOS X to iOS and I'm unable to
>> find the key KCGImagePropertyOrientation.
>
> I notice that
On Fri, June 15, 2012 7:24 am, Luca Ciciriello wrote:
> Hi All.
> I'm porting some CoreImage code from MacOS X to iOS and I'm unable to
> find the key KCGImagePropertyOrientation.
I notice that you keep spelling it KCGImagePropertyOrientation. The proper
spelling is kCGImagePropertyOrientation,
What framework does the documentation for kCGImagePropertyOrientation tell you
to add? In my last mail I said it's right at the top of the documentation page,
as it usually is for all such things.
On Jun 15, 2012, at 9:00 PM, Luca Ciciriello wrote:
> I build using CoreImage.framework and inclu
I build using CoreImage.framework and including CoreImage/CoreImage.h header
The BASE SDK is 5.1 and the Deployment Target is 5.1
The error I get is "Use of undeclared identifier KCGImagePropertyOrientation".
Is there some other header I've to include?
Luca.
On Jun 15, 2012, at 2:41 PM, Rolan
It's in the documentation as iOS4.0 and later and it's in the header file too
grep kCGImagePropertyOrientation *
CGImageProperties.h:IMAGEIO_EXTERN const CFStringRef
kCGImagePropertyOrientation IMAGEIO_AVAILABLE_STARTING(__MAC_10_4,
__IPHONE_4_0);
Did you pick the right framework? It's normall
On Jan 16, 2011, at 2:43 PM, Graham Cox wrote:
> Who complains about a 30MB memory usage increase these days? Who even
> notices? This is not Mac OS 9, it doesn't matter what your app's memory
> footprint is (within reason).
Two kinds of people:
1. Experienced users that watch Activity Monito
On Jan 16, 2011, at 1:43 PM, Graham Cox wrote:
>> It's not like I'm leaking any memory here, so why the large permanent
>> increase? I'd like to avoid it if I can because I'm getting criticized for
>> "using too much memory" despite it not being my fault. :-p
>
>
> Who complains about a 30MB m
On 16/01/2011, at 8:03 PM, Seth Willits wrote:
> It's not like I'm leaking any memory here, so why the large permanent
> increase? I'd like to avoid it if I can because I'm getting criticized for
> "using too much memory" despite it not being my fault. :-p
>
Who complains about a 30MB memory
That's not applicable here. I'm not drawing many many things before returning
to run loop so my memory usage isn't increasing due to repeated calls. It's
just this single image. Just for giggles I tried it anyway, and as expected
there's no difference at all.
--
Seth Willits
On Jan 16
Hi Seth.
You might want to try putting an autorelease pool around your method. See the
"Tip" in this document:
https://developer.apple.com/library/mac/#documentation/GraphicsImaging/Conceptual/CoreImaging/ci_tasks/ci_tasks.html%23//apple_ref/doc/uid/TP30001185-CH203-TPXREF101
I've used this tip
12 matches
Mail list logo
