Filed as FB13531865. Thanks!
FrankSchlegel
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Potsdam, Germany
Post
Replies
Boosts
Views
Activity
I think there is no official API to reset single tips.
As a workaround, you could change the id of the tip. This will cause TipKit to handle it as a new tip and show it again.
I guess it has to do with the affine transform you apply to the image before you do the clampedToExtent():
As you can see, the output of the transform has non-integer extent. This probably creates a row of transparent pixels at the top of the image, that is then repeated when applying clampedToExtent().
To avoid this, you can calculate the scale factors for your transform separately for x and y to ensure that the resulting pixel size is integer.
Alternatively, you can apply the clamping before you apply the affine transform.
Filed as FB13419598. Thanks!
I was wondering the same thing, and it seems that improvements are coming in later versions.
From the comment in the header file:
A NSNumber that specifies the maximum memory footprint (in megabytes) that the CIContext allocates for render tasks. Larger values could increase memory footprint while smaller values could reduce performance.
It basically sets how much memory Core Image is allowed to use (roughly) during rendering. From what I observed, the default seems to be 256 MB.
There is also an Obj-C constant for it.
The -framework CoreImage flag needs to be set in two lines in Xcode, otherwise it will mask the space between the words:
The -framework CoreImage flag needs to be set in two lines in Xcode, otherwise it will mask the space between the words:
The order of the color channels in a CGImage depends on its alphaInfo and bitmapInfo. The default format for 8-bit images is actually BGRA (instead of RGBA) in many places. Where do you get the image from? What's its bitmapInfo and does it differ between iOS 16 and 17?
The issues seem to have been fixed on iOS 17.1 beta 2.
Thanks a lot!
The issues seem to have been fixed on iOS 17.1 beta 2.
Thanks a lot!
Filed as FB13168973. Thanks!
You can also access the tip through the configuration. I think you can simply add a button to your tip layout that invalidates the tip when tapped:
Button(action: {
configuration.tip.invalidate(reason: .tipClosed)
}, label: {
Image(systemName: "xmark")
})
Filed under FB13121690. Thanks for looking into this!