I am working on an app that has two sections, one config section and one result section. My config section needs 2 different views (horizontal and high and yes, I can hear breathing intake from here), with a rotating view for the result. I am not using the Navigation Controller, many pain around the B / C and rotation of layout restrictions.
I am experiencing the joys of rotation experiments and my views are sub-views of my view controller.
See the controller view.ubviews = configH, configV, and the results. I use the controller.View Loudscrew tofranort to bring the configuration, config, or result view to the front.
Rotation work-line (Object of humor) The choirs of angels ... What is happening almost is that my ConfigV button is responsive, but when the device (or simulator) is rotated, then do not have my configH control (Config WVID SubView has been added, but the first one should be brought in front because the app comes in Patrate mode) Controls on the scene of the results also work.
To assign a controller to Plan B, see ConfigH, configV, or the results, all my controls now work, but now rotation is bloated.
Q1: Is there a better way to do this? (See a horizontal and vertical config scene and a rotating result) Question 2: Is there a design problem suggested above, or is it more likely that anything in my own code in my attached brain is missing (something from the Peanut Gallery Too)
Many thanks!
understand it out Removing old scene from IB and creating a new UIUVV from scratch (and reopening it) has determined that painful, but effective looking forward suggests that GKDM went to the same mess:
< P> Thank you all who paid attention to this!
Comments
Post a Comment