I am newbie in Xamarin iOS development.
I created a storyboard, added few view controllers in it.
I added some controls in one view controller, ran the code and checked the output on simulator. All worked great.
Now after some time I checked my storyboard design. Now the controls are not visible in view controller(in story board), but they are visible in document guideline(view hierarchy).
please let me know what should I do to solve this issue.
Thanks in advance.
The problem was solved by clicking on the Portrait/Landscape icon two times which changed the device width to "Compact" and height to "Regular" an in 5 seconds the controls were visible in the ViewController
Related
Using views within my application is causing my storyboard to do strange things. This is making it very difficult for me to make changes. I thought the issue was due to the fact that using a view limits the size of your next view and so on.
However, it's now causing issues where I have to move tableviews into strange places to make them display correctly on the device.
These views both display correctly on my device. However the view at the top is only half the screen. There is also a navigation bar throughout the app which can no longer be seen on my storyboard.
The first view was fine until earlier today when it randomly began displaying as seen below.
Has anyone had this issue before and know how to fix it?
To put it simply, my app has two main views: the first serves to choose some values, the second displays a report. Both are TableView based.
The app looks well on iPhone with any screen size and for any orientation, but since the app’s thought to be universal, I want to get rid of those gaps between elements when the app runs on iPad.
I decided to have the app displaying both views on iPad screen simultaneously as official YouTube app does:
(1) and (2) are the first and the second View controller.
I see it this way:
1) Some initial view controller (additional navigation view controller?) checks idiom (iPhone / iPad) and chooses the next viewController. If idiom is iPhone, the first view controller is pushed.
2) If idiom is iPad, the «new» view controller is pushed. It has two view containers containing the fist view and the second view. Containers have autolayout constraints etc.
Questions:
1) Is it a right idea in context of Apple app design philosophy? What’s the better way to create iPad view combining existing ‘iPhone’ views?
2) Where to check for device type? Shall I use the second storyboard or something? Maybe there’s a good tutorial for this case, I didn’t find one.
Thanks in advance!
For the 2nd part of your question I think you want to look into
I think you want to look into Size Classes and Auto Layout
You can make a single view but depending on the size / orientation of the device - you can enable/disable certain components of the view.
You can pin views so that in portrait you have your 1st layout and in a landscape you have your 2nd layout.
With regards to your 1st question - you do have the ability to embed a view inside of another view
I'm not sure if this is what you are looking for - but as far as what apple is pushing I believe size classes is what they "suggest". You can do a lot. The only thing is make sure you turn on the assistant editor into storyboard preview mode it will help a lot.
All the content of one of my UIViewControllers suddenly stop show in my storyboard, all the objects are grey out in my documents outline and the view controller in question is completely blank, however when I run the code it displays fine in my phone and/or simulator.
I try clean and build the project without any success, any ideas how to fix it?
From your interface builder check the property for specific hidden view as Installed (From Utilities)
I'll try to keep this short and sweet. I have a universal storyboard and my application runs perfectly on the iPhone. I'm having an issue though where I have a view controller with 2 containers, which contain separate tableviewcontrollers.
On the iPad simulator the top table view controller works fine yet the bottom will not scroll or select any cells. Again, it works perfectly on the iPhone simulator.
I cannot for the life of my figure out whats causing this. Anyone run into something similar?
Thanks
Your view might be covered by another view. To make sure your view stays in the front, you can use
[self.view bringSubviewToFront:yourView];
I'm currently using this component in xamarin
http://components.xamarin.com/view/SidebarNavigation and basically it works fine, but when i try to use a UITableViewController as one of my content and add a lot of items in tableview that will basically make the app scroll, the app didn't actually scroll when you run it to iOS simulator, I haven't add any code yet to my contentController and I haven't change any property on my UITableView, just drag a UITableViewController from toolbox set up the code behind controller, storyboard ID, Restoration ID add some data to the tableView then hit run.
I don't know if this is a bug or I'm doing something wrong? any idea everyone? or you can just give me any free component that use as navigation drawer in iOS app.
thanks!
I think it's a bug!
You can solve it by wrapping your uitableview in a uiview.
Just make a fresh view controller and put a tableview as its only child!
Good luck ;)