Post

Replies

Boosts

Views

Activity

Reply to UIPasteControl still asks for permission when it's not the first one on the screen.
Thank you glow! Indeed. This would explain the problems I'm seeing. I redesigned the screen to only have one Paste control on it and it is placed in the dedicated cell with only a help label below it. Even when sizing that dedicated UIPasteControl - until it stopped "touching" the neighbour controls, it was asking for the permission. I can see the point in avoiding obscuring its parts. How can we define the UIPasteControl sizing requirements properly to be sure to give it enough space? I'm trying its intrinsic size and it always returns as zero rect. I'm trying to achieve its size predictability via minimumContentSizeCategory and maximumContentSizeCategory, so it has a predictable size for the different accessibility text sizes. What's the correct way of placing/sizing this control in a storyboard with auto layout? The example here: https://developer.apple.com/documentation/uikit/uipastecontrol?changes=_5 Suggests: pasteButton.frame = CGRect(x: view.bounds.width/2.0, y: view.bounds.height/2.0, width: 150, height: 60) Is it something considered the safe dimensions for the UIPasteControl for all of the accessibility text sizes? Width of 150 doesn't seem to be "safe" - the whole UIPasteControl may not be even shown or it might be raising the permission alert, if the control itself shows. Is it something that needs to be embedded into SwiftUI? Or would it work well in some sort of a container like UIStackView, would this one size it properly for all of the accessibility text sizes? Some pointers would be appreciated so we can build future-proof designs that would not break easily.
Topic: UI Frameworks SubTopic: UIKit Tags:
Sep ’22
Reply to Apple App Store Connect November 2021 payment delayed ?
My payment with the same due date was delayed until Jan 3rd 2022. Company payment came at Dec 31rd, as expected, so I know it is hardly Apple who caused the delay. Looks like "usual" New Year (and any other holiday) bank mess here, in Czech Republic. And then banks have the nerves to back date these in the statements, as if nothing happened. Fingers crossed for your payment to appear soon.
Jan ’22
Reply to UIPasteControl still asks for permission when it's not the first one on the screen.
Thank you glow! Indeed. This would explain the problems I'm seeing. I redesigned the screen to only have one Paste control on it and it is placed in the dedicated cell with only a help label below it. Even when sizing that dedicated UIPasteControl - until it stopped "touching" the neighbour controls, it was asking for the permission. I can see the point in avoiding obscuring its parts. How can we define the UIPasteControl sizing requirements properly to be sure to give it enough space? I'm trying its intrinsic size and it always returns as zero rect. I'm trying to achieve its size predictability via minimumContentSizeCategory and maximumContentSizeCategory, so it has a predictable size for the different accessibility text sizes. What's the correct way of placing/sizing this control in a storyboard with auto layout? The example here: https://developer.apple.com/documentation/uikit/uipastecontrol?changes=_5 Suggests: pasteButton.frame = CGRect(x: view.bounds.width/2.0, y: view.bounds.height/2.0, width: 150, height: 60) Is it something considered the safe dimensions for the UIPasteControl for all of the accessibility text sizes? Width of 150 doesn't seem to be "safe" - the whole UIPasteControl may not be even shown or it might be raising the permission alert, if the control itself shows. Is it something that needs to be embedded into SwiftUI? Or would it work well in some sort of a container like UIStackView, would this one size it properly for all of the accessibility text sizes? Some pointers would be appreciated so we can build future-proof designs that would not break easily.
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Sep ’22
Reply to Apple App Store Connect November 2021 payment delayed ?
My payment with the same due date was delayed until Jan 3rd 2022. Company payment came at Dec 31rd, as expected, so I know it is hardly Apple who caused the delay. Looks like "usual" New Year (and any other holiday) bank mess here, in Czech Republic. And then banks have the nerves to back date these in the statements, as if nothing happened. Fingers crossed for your payment to appear soon.
Replies
Boosts
Views
Activity
Jan ’22