I have a thread with autorun enabled that contains the views manager views and, separately, a window with a placeholder view to add them to it. The placeholder has limitations compared to its inscription and other views in the window, and before using my view controller, I have the size of the window space the way I want. Later I load nib and add its top-level view as a sub-placeholder placeholder, and I also manually create constraints to keep it consistent with placeholder edges.
Everything is fine, and I use this template in several instances in my application, but in some cases, after adding a view, my window changes its size! This is reduced to the minimum size for the added view instead of expanding the view to the current window size.
So far, the only obstacle to this is that when adding a view and creating its limitations, you can also set the view frame so that it gives the initial size for the current state of the placeholder and window. This is normal at the time, but I want to identify more complex complexities that simply line each edge to the supervisor. I do not want to encode frame arithmetic for each of these cases.
Does anyone know what is going on? If the window already dictates the size of my placeholder, and not vice versa, what do I need to do by adding a subview to make the current window size still a priority?
I saw a pop-up menu in Xcode IB windows that seems to be related to restrictions affecting only subviews vs and superview (set to the first for all my feathers), what happens with this functionality? I haven't found anything about this yet.
objective-c autolayout cocoa appkit nslayoutmanager
Pierre houston
source share