I would like to take advantage of using the PopOver segue now available in Xcode 6. I have been experimenting with this, seems very straightforward. However when i add any type of control, label, or any element, and run the project in the simulator, the added elements (controls, labels, etc) do not display. I am running iOS 8.1.2 and using xCode 6, objective-c. The application is targeted for iPad.
I am going from a standard viewcontrler to a viewcontrler,
When i do a standard modal segue, everything is visible.
thanks in advance for any help,
Steve
links to screen shot
https://www.dropbox.com/s/93wt2twuuccbuji/main%20storyboard%20image.png?dl=0
https://www.dropbox.com/s/im4bzlrnrov43cp/from%20simulator.png?dl=0
did you give the anchor point in storyboard?if you want to display second view controller on pressing a button give the anchor point to that button.
Related
I am new to iOS native development and have been struggling for a few days to understand some of the segue concepts. I have tried googling for that answer but I must not be using the terminology Apple has created for this.
I have inherited some code and I am trying to move from the login screen of my app to my first page in full screen. It moves to that page and gives the user that ability to swipe down and go back to the login screen. This is not the functionality that I want. I want to use a button to go back and not gesture functionality.
Assuming you created a "Present Modally" segue, select that Segue and, in the Attributes Inspector pane:
Select Full Screen from the Presentation drop-down.
I'm having a very hard time here.
I created an iOS App in which I have a Navigation controller and a main screen showing a device list and now I'd like to add a detailed view. My issue is, I can't create a segue with action "Show" - the Interface Builds in Xcode only provides options "Push", "Modal" and "Custom"
I'm an absolute beginner in Swift (or for that Apple) development and each and every tutorial I found with google, says, I'd simply have to Ctrl-Click the button, drag it to the new view controller and choose "show" - but there is no :-(
I'm attaching a picture, so you might see more clearly.
Please, if someone could help me out here.
Is my problem caused by choosing Single View Application in the project???
I'm using Xcode 8, Swift 3 and developing for iOS 10 on iPhone
You are likely using the old Xcode storyboard layout, to go back to modern layout:
select Main.storyboard, go to file inspector and check the Use Auto Layout and Use Trait Variations boxes.
I have issue when I try to push view controller in willTransitionToPresentationStyle:. The view was blinking for a split second before it fully expanded. It might be a small glitch or bug since iOS 10 and Xcode 8 are still in beta. But when I manually requested to change presentation style to MSMessagesAppPresentationStyleExpanded by calling requestPresentationStyle: after I push view controller, it went to expand mode more smoothly. Does anyone have similar issue?
I have had similar problems with transitions in iMessage apps. I think this should improve considerably when iOS 10 and Xcode 8 come out of beta, but for now we have to deal with Xcode's bugs.
There's a few things I've done to make this look better. Inside my extension I have a method that checks the presentation style every time the view changes. This method manages two different UIs - one for MSMessagesAppPresentationStyleExpanded and one for MSMessagesAppPresentationStyleCompact. This method hides and shows specific views accordingly. In my compact UI I have a button that allows the user to expand the interface by clicking it (this is basically the same as clicking the up arrow at the bottom right of the screen).
I've noticed that if you let the user expand the messages app after the view has been loaded for a while the transitions are much smoother and less buggy. Not sure why this is the case, but you should give it a try. Also, I've found segues to be extremely buggy, so that's why I went with keeping everything on one view controller.
I have an iOS info app. The main screen of the app consists of rows of icons. I want that after tap on certain icon card with information appears and background blurs. To close the card I need to swipe up or down. It is very similar to Instagram's imageviewer.
Please help me create that.
P.S. This is my first project so please keep this in mind when you going to describe the method.
It should look like this
The answer to your question is probably hidden beneath the layers of how you can segue between the scenes of a storyboard. First, you create a scene like this in the storyboard and use some third party libraries to present it as a 'pop-up'. It is not possible for you to do that natively as Apple has not added any segue style showing the scene like a pop-up on the iPhone screens (On iPad it's possible - check how Apple presents choose Wi-fi network in Settings). For that purpose, you can use BlurryModalSegue or CNPPopupController to perform such operations.
Thank You!
I'm new to iOS development. I used the Interface Builder to add text fields and buttons to my view. When I run the app, the iOS Simulator only shows an empty beige screen. What am I missing? The console doesn't show any error.
It is because you have not connected your view to your File's Owner.
To do this Right Click on the View, Control Click on the Oultlet of your View and drag it to the File Owner.
This shall solve your problem.
Cheers
I reckon it's because you have AutoLayout turned on in your storyboard, but haven't set any constraints.
Follow my instructions in the following article, to confirm if this is true.
AutoLayout problem
Basically, with XCode 6, if you have AutoLayout turned on, you must set constraints on every single control... otherwise your screens will look fine within XCode, but the controls in your screen could (and will) end up anywhere and in any size when the app is run.
It's like designing a beautiful webpage, then displaying it in an angry, drunk, disorientated browser.
XCode is really unintuitive, and unhelpful for beginners... but once you learn the rules of AutoLayout (along with its many quirks), it's reasonable useful.