UIView tree vs CALayer tree
I'm curious, are there any advantages to using a tree of nested CALayers rather than a tree of nested UIViews for a straight boardgame with little animation? I noticed that Apple's GeekGameBoard sample uses nested CALayers and an open source library I've used in the past, Route Me, also relies on using CALayers directly. Just wondering what the typical scenarios are for choosing one method over the other.
CALayers are just bitmaps that you can move around the screen. UIViews have more to them, being UIResponder subclasses. Speed and memory usage are two reasons to use CALayers over UIViews when you don't need an onscreen object to respond to events.
Possibly Related Threads...
|Combo Tree (by SixFellows)||natsirt78||0||279||
Feb 10, 2016 07:55 AM
Last Post: natsirt78
|UIView opaque blending problems||Joecoolage||0||4,097||
Aug 2, 2010 12:58 AM
Last Post: Joecoolage
|UIView Subclass not displaying controls...||flipflop||7||7,640||
May 13, 2010 01:16 PM
Last Post: flipflop
|How to access EAGLView/UIView functions from C?||Rasterman||10||6,942||
Apr 8, 2010 10:47 AM
Last Post: Rasterman
|CALayer won't display||Paul from Boston||1||3,710||
Mar 26, 2010 09:08 AM
Last Post: longjumper