The first half. Ternary has been there since time began. I’ve never seen this part be legitimate before.

Are you referring to the ternary conditional operator, which has existed in Swift since the beginning, or to the fact that it creates a local variable with the same name (myVar) as a parameter or

I just saw someone use this syntax in a project and haven’t see it before. It compiles in Xcode 12.5, but not in Xcode 12.4. Does anyone have any more details on it? let myVar = myVar != someValue

Just to finish up this discussion, below is the code I ended up with for my button that is compatible with both pre-15 and post-15 code. I think that if you subclass UIButton in your current code,

I initially felt that way too, several years ago, when first coming from Obj-C. However, I learned to embrace the tools (which make it easy to find the declaration) and also be mindful of writing

Thanks. I know I don’t need the self, but I want the context. A variable just sitting around tells me nothing about the context in which it exists. I want to see the context and want to see the

Move your `backgroundColor` and `isOpaque` calls to the init method(s). I set up a test project with your code, and that solves the problem. I was going to make that suggestion before I even tested

Hi. I’m trying to draw a bezier shape in CGContext on a UIView in Swift with a transparent background and the background is always black. Nothing online helps. Any ideas? I’ve checked

Hi, Alex. The work-around was to force the button width to be "expectedWidth" (which is the width of the [unwrapped] text + image padding + image width + 8 points of slop (to account for button

And what is, "mirrow above bounds code”?

Could you point out the specific workaround please?

I haven't filed a bug yet, but I will. In the meantime, I've constructed the following work around — it's a hack, but it seems to work.

Can you file a bug? Maybe they will fix it before iOS 15 is released. Jeremy —

Thanks for the heads up. That’s crappy.

Good thought. I'll give it a try. Re: your "do you have to use the API" remark, the simple answer is that if your deployment target is iOS 15, you ARE using the API, whether you like it or not. There

Can you set up an observer to watch and see if it’s changed and then change it back? Seems like a real hack, but it’s a thought.

My god, that sucks. I can’t believe this wasn’t tested. We've actually been building custom UI classes for the past month and am familiar with the pain. Do you have to use the new API?

The problem is unique to the new iOS 15 UIButton API. There is no problem in my logic if the deployment target < iOS15. Specifically, I tried setting a constraint on the height of the button. It is

I did this in UIKit by making the button’s frame.size.width the frame.size.width of the content within + appropriate space buffers. One trick is if the text component is a UILabel, making the lines

I am trying to construct a button using the new iOS15 button API. (Xcode 13ß3, UIKit & Storyboards) The button has a title (aligned .leading) and an image (aligned .trailing). The button has the