Bug 2884 - CGLayer should have a Size property
Summary: CGLayer should have a Size property
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.0
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
URL:
Depends on:
Blocks:
 
Reported: 2012-01-13 10:38 UTC by Tim Dawson
Modified: 2012-01-13 11:27 UTC (History)
3 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 Tim Dawson 2012-01-13 10:38:37 UTC
In objc there is a property to get the size of a CGLayer. A common use pattern for CGLayers is caching offscreen surfaces. At present we have to also retain a separate SizeF variable to detect when the size should change, but the layer itself should sport this property just like it sports a Context property to retrieve the layer's CGContext.
Comment 1 Sebastien Pouliot 2012-01-13 11:18:31 UTC
The property exists but it was not marked as public (typo I guess).
Comment 2 Sebastien Pouliot 2012-01-13 11:27:53 UTC
Fixed in 94774306f7ecf9173ff98e731f0dc84ac9f6ee80 (maccore master)
It will be part of future 5.0.x (stable) and 5.1.x (beta) releases.
Thanks for the report