I am teaching in a team learning focused class and am trying to make a self passed session that will have units. I can't seem to figure out how to set the next slide so I can do the following with my presentation:
1>2>3>4
->5>6>7
->8>9>10
Can you please help me out
Related
I've been wondering for quite some time how Instagram implemented their text editor transition:
On a first guess, I'd say they are performing both the text editing and the "movement" on the same UIViewController, but at the level of complexity they have, they must have found a way to make the transition from VC A to VC B, where VC B does the entire text editing.I'm starting to think that the VC A (movement VC) is holding a "snapshot" of the UITextView, where VC B actually hold the object (then the user can edit it).
I'm not looking for a drag & drop code solution. I'm trying to think out loud about what is the possibilities to implement the same behavior they have, in terms of correct architecture and user experience.
Thank you for your time,
Roi
This kind of problem is best solved using a custom class derived from UIViewControllerAnimatedTransitioning. I've done it before with logos transitioning from one view controller to the next. The official docs are here: https://developer.apple.com/documentation/uikit/uiviewcontrolleranimatedtransitioning and there are numerous examples of how to create a class on the internet.
I was asked to display a list of three options for the user in a View sliding from the top to bottom. They say it should slide from the top because the action is initiated from a dropdown-like button on the navigation bar.
Most of what I found on that subject mentions the deprecated UIActionSheet class.
The "new" way using UIAlertController doesn't seem to allow us to change position of the view. At the least from what I've found.
The end result I'm trying to get can be seen on the image below,
From what I've learned about iOS programming, one method I could think to achieve that would be to create a new UIViewController and to use a custom class to control the transition. But it just seems so much. And I think it wouldn't not look like a dropdown afterall.
The other option would be to create the TableView with options and leave it on the Controller where it should be displayed, configuring its height to zero. And then Animating when necessary. I also have such a bad feeling doing it this way.
Is there a right way to do this on iOS? Does one of the options I've found seems acceptable?
Thanks.
Following the suggestion given by #Losiowaty on the comments, I started looking for a custom View/Control on cocoapods and ended up finding quite a few that did what I was looking.
The one I decided to use is this:
https://github.com/lminhtm/LMDropdownView
I have a 2 UIViewController(s), I need to be able to change the views at the bottom of the Airtime and Data Plan Upon tap gesture on Airtime and Data Plan!
The yellow line will indicate the active view controller. some thing like tab bar.
Perhaps, the image attached is an android version
Could anyone provide a help on how to go about this.
Thanks
I personally use a library called ICVIewPager
https://github.com/iltercengiz/ICViewPager
This is pretty simple and easy to use with examples. It should put you in the right direction without writing a lot of code.
I am a novice at iOS programming, obviously a novice at Swift (as it is new), and a dabbler at best in programming overall over the past ~35 years. I have, however, worked for the past 20 years as a manager of multidisciplinary teams that include programmers and as a result I understand a lot of fundamental concepts of software design. I provide this information for context.
I am working on a database app for a class and adding a lot of functionality of my own choosing to enhance my own learning experience. I yesterday wanted to allow users to tap a UIImageView to choose a new picture for the database entry. I added a Tap Gesture Recognizer to the UIImageView and hooked up the IBAction to the appropriate view controller then added a println() to the IBAction to test whether it was being recognized. Taps on the UIImageView didn't produce the println() and I was frustrated, so I looked around on the tubes for some hints and found some sample code to programmatically recognize the tap:
let recognizer = UITapGestureRecognizer(target: self, action: Selector("didTap:"))
recognizer.delegate = self
view.addGestureRecognizer(recognizer)
This worked a treat, as they say. I was frustrated, however, as I saw a lot of reference to the idea that the code was unnecessary if I was using the storyboard. After a bit of experimentation with a test project, I eventually found that the UIImageView had to have "User Interaction Enabled" in the Attributes Inspector (not the default setting) to recognize user interaction, which in hindsight makes sense.
My question (at last!) is whether the difference between the two approaches is stylistic or whether there is a reason to choose to do it programmatically over the implementation via storyboard. For performance or delegation or otherwise. I can, for example, see that I could embed the recognition code in an if statement. Are there other reasons?
Is this question too theoretical for this format?
IMHO, I always use storyboards unless and until I encounter something that has to be done in code. It's just conceptually easier for me to understand the overall shape of the app if I can see it in large, interconnected chunks. There shouldn't be any noticeable performance differences.
Regarding your particular example, whenever I have an image that has to be tappable, I just put the image in a UIButton, and hook the button up to an IBAction in the controller. This obviates the need for adding a custom gesture recognizer and remembering to make the image tappable.
I am new to iOS development and not aware of lot of features which iOS provides so need your help in building new UI.
Now my requirement is I have A - B - C three controllers where B is homescreen, I want user to pan (pan I mean to say next view controller should come w.r.t to users finger touch ) on the right edge or left edge to go to their respective ViewControllers from B and can come back
along the same line ..
This is my basic structure, I know how to do it with the swipe but then it is wont fulfill my requirment , also to slide the new screen w.r.t to finger is also there.
Try using SWReavelViewController. It is a very easy to use component and will be suited for your solution.
You can find the code HERE
you could get your hands on ViewDeck. It got some more offering than SWReavelViewController. Check this ViewDeck. If anything else is there let me know.