Did I miss the scrolling view part ? Only way you can scroll is by clicking on those buttons after part 4 tutorial is completed. I think either I’m half awake or she completely forgot to implement that part. .
Hi Lea
I’m afraid I’m a little confused by the scrolling too. At the end of video 3 we can scroll the 3 child views (chat, lens, discover) with the buttons but not by swiping with a finger. Video 4 starter project has the swiping enabled but I can’t find the code added since the final project from video 3. How has the finger swiping been enabled?
Other than that I’m loving this series (early days I know) and can’t wait for the App Store and Map chapters.
Yes, overriding the hitTest function is what makes the user able to scroll because we’re passing through the touches. Sorry for the oversight of not mentioning that addition in the course!
What’s more important, though, is making sure that we capture the scrolling behavior (which is what happens at 4:27 to the end of video 4) in a way that lets us use the specific scrolling values to drive the pertinent animations.
I’m sorry that your final project doesn’t scroll. I’m a little confused why that would be happening because it does scroll for me when I download the files. I am using Xcode 10, which is the Xcode used for this course, but after I make some adjustments (mentioned in the comments for this part of the course), I can also scroll just find on the project ran through Xcode 9.
I’d have to test your project specifically in order to troubleshoot further.
Hello!
I have the same problem. I thought that it was a problem with XCode 9.4. But I have installed Xcode 10 beta and the same problem is presented.
EDIT:
The problem is with NavigationView, it handles touch events.
Yes! If you download the materials from the video part you’re on, the function is already added. I recommend, in general, to download the materials for the specific videos and not just assume that everything that we add will be covered - unfortunately there’s just not enough time in these 10 minutes videos to go through everything.
Did you initially download the project files from the 4th video? If not, we don’t include adding the hitTest function in the video, so you would be left without it.
I recommend downloading the materials for each video specifically.
Thank you @leamars, I will do that as the forum acts up on Chrome browser too. I am using the RW site on Safari.
I need to ask a question related to UI with all the animations on the Apple Store part. We only used DispatchQueue.main in the last part to delay the UI animations and we did not need it before, is that because all the other functions and delegates used in process account on work thread?
I remember in the Animations book that you have to always enclose all the action on main thread.
Hey @albaqawi for your animations questions with the DispatchQueue. I’m not entirely sure what you mean.
All UIKit work, including animations, should always be performed on the main thread. When we’re doing UIKit standard UIKit animations, any work that has to happen after the animations completes can be put in their completion block. We’re using DispatchQueue on the last part of the scrolling, because it’s not technically an animation. The values there change based on the user input. We’re using DispatchQueue there simply to avoid the jerkiness of the dismissal animation and give a little bit of delay before that happens so that the dismissal is not as jarring.
I’m not sure I answered your question, so please let me know if there’s something else I can clarify.