Post

Replies

Boosts

Views

Activity

Reply to macOS 11 beta created an Update partition that is still there after installing the official release
I think it's extremely sad that nobody at Apple wants to help me out here. Is it intended that we install official things that leave garbage around and not even the developers are keen to point out what it is, or to show that they even care about what happens to our machines after installing their software? (Yes, I submitted a bug report 1.5 years ago, in June 2020, obviously without response.)
Topic: App & System Services SubTopic: Core OS Tags:
Dec ’21
Reply to Why does Apple not mark solved bugs as solved?
I've already filed a bug report months or years ago, I don't remember exactly, but never got a response. Why should it be up to us to keep track of what's solved and what not? After all, for some of them I get a response asking to verify if it still happens in the newest OS release, so they have a mechanism for tracking what they are working on. I don't know about you, but checking regularly if any of the thousands of bug reports that I filed have been solved would take many days (I actually did this last January, during the holidays). I would have thought that since we're helping them in finding bugs in their products it shouldn't be our burden to keep checking them. How inefficient that would be!
Nov ’21
Reply to Wrong colours when rendering SKTexture
I've noticed this as well and filed a bug report to Apple exactly 6 months ago, still without answer. It is easily reproducible with this code:         let url = Bundle.main.url(forResource: "art.scnassets/texture.png", withExtension: nil)!         plane1.firstMaterial!.diffuse.contents = url.path         let node1 = SCNNode(geometry: plane1)         node1.position.x = -5         scene.rootNode.addChildNode(node1)         let plane2 = SCNPlane(width: 10, height: 10)         plane2.firstMaterial!.diffuse.contents = SKTexture(image: NSImage(byReferencing: url))         let node2 = SCNNode(geometry: plane2)         node2.position.x = 5         scene.rootNode.addChildNode(node2)
Topic: Programming Languages SubTopic: Swift Tags:
Jun ’21
Reply to AVPlayer.timeControlStatus and AVPlayer.rate are wrong during fast forward or backward
Thanks for your help, but I don't get what you mean with this: When a user scrubs, seeks, fast forwards, rewinds, uses trackpad or touch gestures or key bindings that would result in the AVPlayer changing times we may set the rate to 0 during the operation, but in most cases we will restore the rate thereafter. Who is "we"? Is it AVKit or I the developer who uses AVKit? If you really mean the latter, then why would we set the rate to 0? And how would we intercept all those operations, when AVPlayerView already does it? checking that the AVPlayer's rate is 0 or timeControlStatus == .paused should be sufficient for determining whether the video frame is not changing As I said, timeControlStatus == .paused is true even when the user plays fast forward or backward (by pressing L twice or J after pressing the play button) and even if during this time the pause button is shown and not the play button. I would have expected that whenever the pause button is shown timeControlStatus != .paused and rate != 0. In the end I really just want to know if the play or pause button is shown, so that I can react to changes in other views and seek to another frame only if the play button is shown and the user is not expecting the video to keep playing.
Topic: Media Technologies SubTopic: Audio Tags:
Oct ’20