Bug 15516 - CALayer.Contents and CAKeyFrameAnimation.Values
Summary: CALayer.Contents and CAKeyFrameAnimation.Values
Status: RESOLVED FIXED
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Library (Xamarin.Mac.dll) ()
Version: Master
Hardware: PC Mac OS
: Normal normal
Target Milestone: 1.12.0
Assignee: Chris Hamons
URL:
Depends on:
Blocks:
 
Reported: 2013-10-19 14:47 UTC by Jérémie Laval
Modified: 2015-01-23 10:16 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Jérémie Laval 2013-10-19 14:47:08 UTC
Short story:

  - CALayer.Contents can also accept NSImage instance (from docs: "In OS X 10.6 and later, you can also set the property to an NSImage object.")
  - CAKeyFrameAnimation (and friends) should accept CGImage (and other CG types which are not NSObject based) in their values property.
Comment 1 Jérémie Laval 2014-07-22 21:15:49 UTC
This is still not fixed
Comment 2 Chris Hamons 2014-11-06 16:01:46 UTC
This was more tricky that expected. I have it fixed locally waiting for code review.
Comment 3 Chris Hamons 2014-12-08 11:33:13 UTC
Done - maccore c9ddeb8408ab5891032cbbff8dc90e96784320c4 and xamcore d7b9af5ad9a7b0e2707a42eb3b8e5adb1a027559 master.
Comment 4 Rajneesh Kumar 2015-01-23 10:16:41 UTC
I tried to verify this issue but not sure about the steps to verify this issue. Could you please share the steps with us, to verify this issue. That would be very helpful to verify this issue at our end. 

Thanks.