I am trying to put a UIImageview on top, and two UITextFields follow underneath it. All are confined with Constraints, and it was working fine a few hours ago. But Something weird is happening now. I run the app, and the View comes around but there is no ImageView or where the UITextFields were supposed to be, they aren't visible there anymore, but when i click on that position, the Keyboard pops out, which means there are both UITextFields here but somehow can't be seen. I've cleaned, deleted derived data etc but nothing is coming around. Any idea?
So here are two snapshots that explains that the image "launchSplash" is coming over the other elements. How could I make it go back?
Thank you everyone for helping me out here, it was a mere change or hierarchy of in my Storyboard UI. I didn't put them in the order required and was experiencing this bug. Here are attached snapshots of the new working order of elements in my View Controller.
Thanks again for all your help, Inspecting sure is helpful and fun :)
Related
When trying to view a larger UITableView inside of a UIViewController in the storyboard, I can only see/edit the top most cells from the table. The moment I scroll further down the cells are all blank. This is purely for storyboard, the code works fine when running, but any cells in the storyboard that are further down a tableview I can no longer edit since they show as blank.
Here's an example to illustrate
As can be seen from the shift right click, I can't even select the cells that are there.
I know and have experienced problems such as not being able to scroll at all before, such as this, but this is different as I can scroll down but cannot see the rest of the cells of my tableview. Has anyone else ran into this problem, and would know a solution? It seems like it may have something to do with Xcode 7, as I recently upgraded to it.
Although not ideal, I've found a few work arounds for this problem. One solution is to make a temporary UIViewController with a UITableView, and then drag cells into the temp UIViewController until the cell you want to edit is visible. Once you've changed it, drag all the cells in the temporary view controller back into their correct controller. This is extremely hacky, but so far is the only way I've found to visibly see the cell.
Another thing that can be done is that the cells are still editable in the document outline, meaning constraints and elements can still be modified from there. However, it is difficult, as I wasn't able to see the cells being edited, they still appear to be blank.
Hopefully someone else finds/knows of a solution to this and can post it, I'll leave these two workarounds up though they're far from ideal.
I created a new Xcode6 project and things were great.. but then I copies a few view controllers from an old project over. Now those views have an odd black bar appearing at the bottom of the view when I run the app on a device or in the simulator. Its transparent on some devices and not on others. They all have "bottom bar" set to none.
I tested this out by re-creating one of the views and the bar is gone. has anyone run into this before? If so, is there a setting to change to fix it? I have been looking through the source code version of my storyboard and see nothing that will help. Its not any constraints I have set because 1 of the views is nothing but basic tableView with no changes or outlets.
I know the "solution" is to recreate all views I copied over. However, I spent a great deal of time on setting each individual subviews constraints on a particular view controller. So if I am missing some simple setting my time wont be wasted re-setting up this VC.
Thanks for any help given :)
So I have an existing app I'm working on for a friend...
and let's say I double click on animals_real and I get this screen...
Basically all I want to do is create a back button back to the home page on the animals_real page and all the other ones like it(body_parts_real, cleaning_real, etc.) but for whatever reason I can't find the xib file or the code for it and I'm not entirely sure what file it would be in. Also, since I am fairly new I'm not entirely sure how to implement the back button. Any help is greatly appreciated.
----------------------------------EDIT 1------------------------------------------
The main page works under ViewControllerForIphone.xib and the settings page is under SettingViewControllerIphone.xib. This led me to believe that the other pages would be under the SubPECSViewController_iPhone.xib. However, if I go in and edit that it doesn't change anything when I run the simulator. So, basically I have been trying to understand UIScrollView better and how it works but I am kind of just stuck.
Welcome to iOS. Other commenters will point out that you should start here at the UICollectionViewDelegate Reference (which you can also get to through Xcode (shift+command+0)
Basically, a uicollection view populates itself based on some array of data.Look here to see what's going on
(void)insertItemsAtIndexPaths:(NSArray *)indexPaths
When you tap on animals, this method is called:
– collectionView:didSelectItemAtIndexPath:
Some logic happens here, and I'm presuming you load the collectionview from yet another array.
To solve your original problem of a "back button," you might simply want to reload the viewcontroller's original datasource or possibly "pop" back up the navigation stack. Again, without seeing at least part of the code, there's very little we can do except speculate :)
I have a simple application with a view controller consisting off 3 UITextFields, a DatePicker and a Segment Control.
I have spent a ton of time getting my ViewController scrollable with AutoLayout and a UIScrollView (entirely in Storyboard). The problem I'm getting now though is when I start typing in any one of the UITextFields, I'm suddenly not able to type in any of the other text fields, though I can dismiss the keyboard, select dates in the DatePicker and select segments in the Segment Control.
This was of course not the case before implementing the scroll view and this is only occurring on the actual device rather than in the simulator (emphasising the importance of testing on a device).
I have read through a few SO answers but none of them seem to work.
Please see a screenshot of how my views are set up:
I've also gone onto the UIScrollView and ensured the following three are unticked:
I've enabled and disabled each of them individually but with no luck.
It took a ton of time to get the AutoLayouts working so I honestly hope I won't have to adjust too much here.
My thinking is that because I'm trying to click on a textField, perhaps the View is treating that as I'm wanting to scroll also. Though of course, when I first invoke this view controller, I can click on the 1st, 2nd or 3rd TextField while scrolling, so that makes sense no sense.
One SO question said it was a bug during the iOS 7 beta phases, but my device is running iOS 7.0.4.
My scrollview doesn't have an outlet because this entire procedure was done using Storyboards, but I'm happy to create one if need be.
Reading the Apple docs, it looks like delaysContentTouches is exactly what's required here, but that's turned off in my UIScrollVIew.
Basically any suggestions or assistance with this would be massively appreciated - it's driving me mad!
Is there a way how to remove those two "darker" -ish places above and beneath active table? I have already tinkered with Opaque options without any success.
Note: The screenshot is taken while "dragging down".
Michal, I'm having trouble understanding how this is happening. I tried a similar setup on one of my view controllers in a storyboard. On the left you can see the result and on the right you can see how it's set up in the storyboard. As you can see, this is a standard UITableView with static cells without the "dark background" issue. This also doesn't appear while dragging down.
This could be caused by something that's wrong with your setup. Could you elaborate so I can help you?