Posts

Post not yet marked as solved
0 Replies
380 Views
I had a Lab session today and was asked to continue the discussion on a next Lab session Friday but there isn’t one left for Interface Builder and Auto-Layout so I will post the Lab I’d to see if they can still reach me -  Lab ID PQ24KHJ2N2 The Question: I have an array of buttons over certain spots of an image. When the user clicks one all the others get hidden. All woks fine even in landscape except for bigger iPhones. Then some buttons do not follow the auto-layout scaling of the image underneath them. I would like it to behave as pin points on a map and to continue using only storyboards. Not sure if this correlation between image and buttons is possible even through code.  Any possible work around? I can show my storyboard if needed.  The image is on a Scroll View and the buttons on top of a container I’m looking for a way to image and buttons scale together proportionally.
Posted Last updated
.
Post not yet marked as solved
0 Replies
534 Views
We have around 2,000 catalog .jpg photos in 2D of fitness equipment (with no background). When we take photos of real ones we would like to identify if the photo taken is of the same kind (not a car or a motorcycle) and also blur it’s background. blur backgrounds is easy with Vision in portrait mode but for human faces.. What is the best approach to be taken in this scenario.? We would appreciate some pointers or guidelines. Thanks!
Posted Last updated
.
Post not yet marked as solved
0 Replies
439 Views
We have an App which displays a human body image on the background with 2 kinds of buttons over it. One type is the names os the muscles the other are rounded spots with their location on top of the human figure. When the user clicks the muscle name all spots disappear and only the one over the muscle remains. All was good when only a couple of iPhone sizes existed but now we cannot figure out how to make auto-layout work like this since the image's proportion in the background doesn't scale the same way as the buttons. It will a be a missed feature having to leave this out.. Should we just go for SwiftUI instead? (sorry if this isn't the right place to ask)
Posted Last updated
.