Is it expected behavior that when applying a CATransform3DMakeScale()
transform to a CALayer the layer's current bitmap information is what
gets scaled (using some type of filter) rather than asking the layer
to actually redraw itself into the, presumably, freshly transformed
context?
On Jun 11, 2008, at 8:56 AM, Brian Christensen wrote:
Is it expected behavior that when applying a
CATransform3DMakeScale() transform to a CALayer the layer's current
bitmap information is what gets scaled (using some type of filter)
rather than asking the layer to actually redraw itself
On Jun 11, 2008, at 12:37 , David Duncan wrote:
Effectively a CALayer represents a texture with the layer's contents
on the video card. As the docs say, transforms only affect geometry.
The texture does not include geometry, thus the current content is
scaled rather than being re-rendered.
On 11 Jun '08, at 9:37 AM, David Duncan wrote:
Effectively a CALayer represents a texture with the layer's contents
on the video card. As the docs say, transforms only affect geometry.
The texture does not include geometry, thus the current content is
scaled rather than being re-rendered.
On Jun 11, 2008, at 12:39 PM, Jens Alfke wrote:
Are all layers treated as bitmap textures, even solid ones? For
instance, if I create a 1024x1024 layer as a background and just set
its background color to blue, does that allocate a megapixel's worth
of VRAM? What about if I add a border
