Bug 3579 - Can't set CAShapeLayer Color and Path properties to null
Summary: Can't set CAShapeLayer Color and Path properties to null
Status: VERIFIED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.2
Hardware: Other Other
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-02-22 03:39 UTC by Jamie
Modified: 2012-02-29 12:38 UTC (History)
4 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:
VERIFIED FIXED

Description Jamie 2012-02-22 03:39:04 UTC
When I try to set a CAShapeLayers FillColor property to null I get a null ref exception.  According to Apples documentation I should be able to do this.  

The same issue occurs when setting the Path property of CAShapeLayer.
I suspect this is an issue with a lot of the CoreGraphics namespace as a lot of the property setters use value.Handle without a null check on value.

A workaround is to do the following:

ShapeLayer.FillColor = new CGColor(IntPtr.Zero)
ShapeLayer.Path = new CGPath(IntPtr.Zero)
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-02-22 07:25:09 UTC
Fixed in 8029651 (master). This fix will be included in the first 5.3 release.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2012-02-27 12:33:20 UTC
It will also be included in 5.2.6.
Comment 3 Eric Beisecker 2012-02-29 12:38:24 UTC
Verified Fixed in 5.2.6