Hi!
I'm having a catch-22 kind of issue, need some perspective on it.
Just updated to High Sierra, which wierdly forced a new version of Xcode onto my System (I was already running the latest)
anyway, i hit compile, and I get a few wierd runtime errors.
one of them, happens when I add a Layout manager to my View's layer (a CALayer, backing the view)
I learned some time ago, that you destroy the view, and render it worthless if you change the view's layer, a great many things particular to that view are wiped out, never to come back. and so instead, I add a subLayer, and I constrain it to the size of the base layer, and work from that.
Now I can't do that, because without a layoutManager, the view's layer can't address the constraints, so my sub layer sits at the bottom left of the view... pretty worthless.
see? catch-22. you can't assign a layout manager to the layer backing the view, so you can't control the layout of any sublayers of that layer. How is this supposed to work? Because it doesn't take any effort to see that Apple doesn't intend all CALayer based Desktop solutions to lose the ability to be laid out.