In the book it says I need to open the ExploreCell.swift. Seems you are not using a book fit for the latest Xcode. You should better find another book which matches the Xcode you are using.

Can you create and share a simplified project which can reproduce the issue?

Okay I will look at my code again, I will recopy it. Thanks. I have copied all the code you have shown in this thread, modified some methods as I have shown. (And I needed to fill many parts to make the project build and run.) And then replaced some parts to provide some test data and I could not reproduce the issue you have described: there are issues with selectedScope 0, When I filter for a specific player in selectedScope 0, I see multiple cells of the same player instead of one. When I delete all character it should clear and reload one of those fetch methods instead of giving multiple cells of the same player. After I delete all characters and when I try to start typing again in the searchBar I see no cells shown. If you could show some info why all those things were happening, I would try to solve the issue, but currently I have no clue what's going on.

a button called "itemOneDelete" I guess you have two different kinds of itemOneDelete, a button and the method itemOneDelete(_:). And Xcode is assuming itemOneDelete as the method, not the button. Generally, Xcode can distinguish the two things if you declare them properly. Do you have the IBOutlet declaration of the button itemOneDelete? @IBOutlet weak var itemOneDelete: UIButton! Or else, there may be something wrong in the other parts of your code. Can you show whole code of your view controller? By the way, your question has nothing to do with the SwiftUI framework. The tag SwiftUI is not appropriate for your question.

it trims from right to left, It is not the right description of trim(from:to:). It trims from the start of the path to the end of the path. With your Raindrop, this code: Raindrop() .trim(from: 0.4, to: 0.6) .scaledToFit() would show you the lower portion of the path. If you want to cut arbitrary shape with some band from top to bottom, you may need something other than trim(from:to:).

I copied it exactly how it was written and it does fix a few things while giving me a few more issues. You may be doing something strange beyond my guess where you have not shown yet.

Okay I tried your solution but there are issues with selectedScope 0, I cannot reproduce the issue you have described. You may be doing something wrong somewhere.

Under the dialogue shown with File New File..., you can choose: iOS/Cocoa Touch Class macOS/Cocoa Class ... And then you can choose Objective-C as Language in the Next view. Isn't it sufficient?

I want to trim it 50% but from top to bottom, so I want it trimmed from the center to the top. Thanks for your reply. In fact, I expected some more info about all the views in your app, if there is any other views overlapping to your shape or how your shape is arranged in your app, etc... Sorry, my words are not enough. So, assuming the simplest case, you may use clipShape. Define your clipping rect, for example: struct RectBand: Shape { var from: CGFloat var to: CGFloat func path(in rect: CGRect) - Path { Path { path in path.addRect(CGRect( x: rect.origin.x, y: rect.origin.y + from * rect.size.height, width: rect.size.width, height: (to-from) * rect.size.height )) } } } And use it with clipShape like this: Raindrop() .clipShape(RectBand(from: 0.4, to: 0.9)) .scaledToFit() Of course you may need to adjust the values from and to.

 Isn't there any other cheaper alternative? Re-installing is cheaper, it is free. You will not lose your data if your app properly persists the data.

Is this conclusion correct? If not, what I need to do? Partially correct. Your developing apps installed via Xcode have some fixed period of days available. If you do not want to pay for Developer Programs, you may need to update your app and re-install it using your Xcode.

What would you use or how would you do it? That depends on how you want to use the trimmed shape. Can you describe how you want to use it more specifically?

Yes, my project compiles OK for me if I remove those lines that try calling fooTest() or try setting self.player.meteringEnabled Thanks for your reply. Then the issue may be different than I guessed. The Github project compiles ok It does not have any meaning if the original ObjC only project would compile or not.

As far as I tried, the GitHub repository you have referred lacks the right definition of protocol MYAudioTabProcessorDelegate and does not compile. Are you sure you have fixed the issue and your project compiles successfully when you remove self.player.meteringEnabled = true (and all other self.player.... parts causing the error)?

I was wondering the same thing about exit(0). Quite a few people say that would be rejected, Old App Store Review Guidelines had an explicit description about quitting apps which can be interpreted as apps should not quit itself, and as you found, there were some reports that apps had been rejected because of exit. I cannot find the same description in the latest App Store Review Guidelines - https://developer.apple.com/app-store/review/guidelines/ nor the latest Human Interface Guidelines - https://developer.apple.com/design/human-interface-guidelines/. You should better read them carefully (maybe you have read them several times, then once again), and you can challenge if you think it to be safe enough to use exit, with your own risk.