This is only a half-baked idea, but it would be cool if a view's implementation of -instrinicContentSize could somehow use the same signal chain that the view uses for laying out its subviews.
It seems like this would involve some sort of redirection, so that:
- Live inputs – like
self.rcl_boundsSignal – are zeroed out or somehow mocked, to ensure that they don't factor into the size calculations.
- Output bindings – e.g.,
RAC(self.subview.frame) – are disabled, so no layout is actually performed.
This is only a half-baked idea, but it would be cool if a view's implementation of
-instrinicContentSizecould somehow use the same signal chain that the view uses for laying out its subviews.It seems like this would involve some sort of redirection, so that:
self.rcl_boundsSignal– are zeroed out or somehow mocked, to ensure that they don't factor into the size calculations.RAC(self.subview.frame)– are disabled, so no layout is actually performed.