When I use ConstraintLayout as root view group, and when keyboard is being showing, my views in the root view don't up as with RelativeLayout and others layouts, not important which options I set in manifest.xml for android:windowSoftInputMode... Do you have same problem? It is possible to solve it? Thanks
Related
I am stuck in a screen where?
I have two UITextFields at top and one UIButton at bottom.
I have used IQKeyboardManager library so it is possible to scroll the entire page (till the bottom button) with keyboard present on the screen with the help of IQKeyboardManager and without use of UIScrollView.
Though I have set layout constraint of IQKeyboardManager which is IQLayoutGuideConstraint to my bottom constraint but it is not working for me.
self.IQLayoutGuideConstraint = self.bottomLayoutConstraint
Please help. Thanks in advance.
This is something that I've brushed off for a while now, but needs to be fixed. Recently, I upgraded to Xcode 5. After the upgrade, the buttons on the initial view will move after being clicked. This only affects that view, and none of the other views. This is odd, because the main view has no attached code to it - it is just a default UIViewController class. I tried creating a custom UIViewController class and linking the view to it, and I've tried deleting the button and recreating it - but they still move when clicked. Has anyone else had this problem after they upgraded to Xcode 5?
Before I click a button
And after I click a button
I suspected the problem is with the new Auto layout and the constraints. I have had similar issues with this when an object redraws it moves. Normally mine are when I expand a NSWindow (OSX) the objects inside its view fly off into a different position.
I would suggest you read the Documentation on Auto Layout guide and then have a look at how your buttons are set up. The is also a section on how to debug issues.
This is most likely happening due to auto layout. You have two options:
Add auto layout constraints that will position them in fixed positions, so that way they will never move.
Disable auto layout for your storyboard or XIB that contains the view controller.
I need to design a view in which I want to create a sub view which should show like menu in Android, When we click menu button in Android mobile, an vertical view will pop up(that occupy part of its parent view) and it will get focus.. same thing I need to design in IOS. Do I need to create a view and add as subview, or Is there anything we can do other than that? Please suggest me some ideas for that..
thanks.
Add an semi-transparent UIView over your top view, on which you can place / design components as you wish, user interaction with anything below it won't be available, and you'll create the menu impression, because the user will be able to see the view below as well, even though it will be greyed out and non-usable, until you remove / hide the overlay view.
Support for menus was added in iOS 13 & more in iOS 14. See UIMenu.
I'm new to Xcode, and I'm having issues with Xcode auto-resizing controls when I add them to a view. Literally every control I try to add to the view is resized to fill the entire view, and I cannot figure out how to manually resize the controls and/or disable resize to fill in the first place. How does one go about this?
Thanks for any help :)
Ah. In a fit of noobishness, I failed to realize that I was adding controls to the view controller. Whooooops.
I am working on a GUI in Interface Builder for an iPhone app.
In my view controller, I would like to have a toolbar at the top and then some controls (i.e. a view) that are centralized in the lower portion of the view.
The problem that I am having is that I want things to be centralized in the area below the toolbar but the whole screen size (including the toolbar) is being used when centralizing.
Any ideas how to effectively achieve this type of layout - it must be pretty common but I haven't found anything yet.
Thanks,
Alan
You might want to try putting all your control area below the toolbar in a separate subview, since that subview might do what you want as it resizes.