Does anyone know how CNN is doing their top pull down menu?
It looks like a UITableView that is called with a touch drag event but wasn't sure. Googled various keywords but was not able to turn anything up. Just looking for some guidance on how to replicate this behavior.
I've no idea how it's actually done, but I know how I would do it: any view can sit completely or partially offscreen and be dragged onscreen by the user in the usual ways (e.g. a swipe or pan gesture recognizer). There's nothing special about that.
I guess they are doing something like https://github.com/mikefrederick/MFSideMenu
You have to customize "MFSideMenu" a lot though. If you dont want to show this menu on every view you need to disable UIGestureRecognizerDelegate on that view.
There is also something like https://www.cocoacontrols.com/controls/pullableview but you may need to add UIGestureRecognizer to this class.
Related
It seems like there should be a simple answer to this, but my searching doesn't turn up an answer.
I have a few controls in a UIViewController that resides in a Container View within another UIViewController. When a user taps one of the UITextFields, all the controls in the container view controller move up to accomodate the keyboard being present. I DO NOT WANT THIS ACTION. I simply want them to stay put. I've tried a lot of the obvious solutions, but none are satisfactory.
I have tried some solutions to counteract this behavior, including catching the Notifications for keyboard events and trying to counteract the animations. I do not want a quirky anti-animation. I simply want the controls to stay put when the keyboard is dispatched.
It seems like nowadays (with iOS 6.1) there should be a way to do this just with IB, but I do not see one.
Edit: For example this post: disables the animations, but the controls are still relocated. I do not want them to move at all. Moving them back to their original location is not ideal, rather disable them from moving at all.
It seems like back in iOS 4 or so, you had to move the keyboard yourself, manually. Now it's done automatically, but not always desired. I just want to disable it.
I would like to customize the animation to display a uipopovercontroller so that it can slide in from right to left when it appears. I basically would like to simulate the menu you can see in Flipboard. Is there a way to customize the animation without having to write a popovercontroller? It seems that the default behavior has the slide in functionality but it is too fast to see it happening. I didn't find any property where i can set a transition style.
Any help would be greatly appreciated!
I'm afraid that isn't a popover that the Flipboard app is using. It's most likely another UIView or UIViewController layered on top of the current view. Much like the 'About' menu in Angry Birds. Animating UIPopovers is also not going to be very easy, as they were never built for customization (or to be leak proof, or to even be very good in the first place). My advice, create your own. (I love github, so so much).
I want to create view in which when user use in portrait mode then two images scroll in scroll view and when user change mode as landscape then both image views add and become single view. I show this function in restoration hardware apps.I like that so i want to make my apps like that? how do that?
What you ask, is a simple implementation that I could do for you. But then again, you would't learn anything and you would probably come here and ask again. I won't give you the fish, I will show you a way of catching it. Check this tutorial, to learn how to handle rotation and then manipulate your views the way you want:
http://red-glasses.com/index.php/tutorials/iphone-auto-rotation-for-intermediate-developers-tutorial-1/
In my profile you have my personal email, after you learn that, if you need more help, count with me.
So, in an iPhone app I am working on, I've decided that the best way to display all the contents to the user is to have the top part of the screen show some information, and the bottom of the screen show different information. However, the bottom part will change sometimes, so I was working on implementing that.
Another app that does this is the MTGLife app, here are some pictures:
http://picasaweb.google.com/lh/photo/HILMaJPnbLxP6hQRkn_6XA?feat=directlink
http://picasaweb.google.com/lh/photo/d5wpS8x_aRyAEOBpYYIxwQ?feat=directlink
http://picasaweb.google.com/lh/photo/RW-BQfqx-VytRim3BxeRZQ?feat=directlink
You see that upon hitting a button, the picker switches over and displays the log. Hitting the same button switches them back, with a pretty animation. I would like to do the same thing in my application. I'm not sure the best way to go about it though...
I was thinking that I would make 2 UIViews, and then would simply flip between them, but I want to get some opinions first on how to do this, and then a push in the right direction.
Thank you!
The 2 UIViews is a good approach. By using the UIView animations functions, you can switch between the Log and the Picker with the desired transition.
In the UICatalog sample application (see TransitionViewController), there an example on how to animation two subviews
When I've learned that I have to write some code to make the iphone keyboard go away. I was quite surprised. I was surprised even more when it become apperent that it is just the top of the iceberg.
What are the expected UI behaviors that aren't provided by system OOTB?
Is the list below complete?
The expected UI behaviors:
Focusing next text field when [done] is hit
Hiding the keyboard when background is hit
Using Touch Up Inside to fire a button action. (To give user opportunity to change his/her mind)
Supporting the screen rotation.
Some of that is silly, but some of it has uses as well.
Focusing next text field when [done] is hit
Which field is "next"? If you have a large form with fields both next to and above/below each other, next might not be so obvious. Even if they are in some linear layout, the iPhone would have to work to figure out which one is next. Do you want to wrap around at the end of the form, or dismiss the keyboard, or submit the form?
Hiding the keyboard when background is hit
I mostly agree with you here, though there are a few cases where this is useless. For example, adding a new phone number in the contact app.
Using Touch Up Inside to fire a button action
This one I really don't get. I can only guess that it's designed to allow you to use buttons instead of the touchesBegan/Moved/Ended methods. I guess it could be useful, but I've never used anything but Touch Up Inside.
Supporting the screen rotation
Many apps just don't work in any other orientation, such as games. If you want to use rotation, you only have to add two lines of code assuming you've done your layout well.
I hope this helps explain some of the strangeness. Aside from the keyboard dismissal, I've never really found anything too annoying. The one thing I wish they supported was using the highlight state of UIButtons for the set state. It would be a quick and easy toggle button, but I've taken to screenshotting a highlighted button and using that for the background image of a selected button.
Want a rounded rectangular button that isn't white? Since that one uses a background image, you can't just click something somewhere that makes it the color of your choice. You have to create your own image or you could even use CSS (WTF!?) to do it.
Unfortunately, the iPhone SDK lacks a lot of helpful things one would think would just be there. However, many people have taken the time to write wrappers for many of these kinds of things to help facilitate development - a quick google search into the functionality you are expecting may turn up a lot of useful answers!
For example, you could make the keyboard go away when you tap outside of it by creating a new view when it appears, and placing that view behind any user-interactable views on the screen. When that new view is tapped, it will become first responder and cause the keyboard to slide away (because the UITextField is no longer first responder).
Such a thing could be easily implemented as a drop-in fix for pretty much anything you'd need it for with very little code.
Still should have been included in the SDK in the first place, though!