• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [Q] Cocoa Binding for filters applied to CALayer (JongAm Park)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Q] Cocoa Binding for filters applied to CALayer (JongAm Park)


  • Subject: Re: [Q] Cocoa Binding for filters applied to CALayer (JongAm Park)
  • From: JongAm Park <email@hidden>
  • Date: Wed, 29 Aug 2012 15:32:04 -0700

I found somewhat interesting behavior.

When it doesn't use property to set an instance of CALayer like this :

     m_imageLayer = [CALayer layer];

instead of

	self.imageLayer = [CALayer layer];

it doesn't cause the problem anymore.

Instead of using property, I tried to use a setter and a getter methods for being sure like :

- (void)setImageLayer:(CALayer *)layer;
- (CALayer *)imageLayer;

 [self setImageLayer:[CALayer layer]];

Then it presented the same problem.

So, somehow CALayer looks to be assigned directly instead of using properties.
Once assigned directly, it doesn't matter whether to set filter by [self.imageLayer setFilter:...] or
[m_imageLayer setFilter...]

Is there any reason why it works like that?

Thank you.
JongAm Park
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: RE: ARC Issue in new Sketch Sample Code
  • Next by Date: Re: Sandboxing die.die.die
  • Previous by thread: NSData DataWithContentsOfURL within a protocol handler
  • Next by thread: Apple Mach-O Linker Error
  • Index(es):
    • Date
    • Thread