Trying to wrangle Core Animation, DirectComposition, and Wayland under a single API is making me yearn for the good old days of working around bugs in Qualcomm GPU drivers. At least I only had to work around one set of bugs…
Right now CA is causing me a lot of grief due to CARenderer (yeah yeah I know, but we can’t ship Metal yet), but I think they’re all about equally problematic in different ways.
-
-
Do the other ones handle offscreen rendering differently? (truly don’t know)
-
I’m about to find out! :)
-
This is for integration testing, BTW, so I could in theory just give up, but I do want some kind of automated testing here…
-
Is rendering to a window and screenshot-ing impractical? I wouldn’t be surprised if CARenderer gives surprising results sometimes…
-
I tried that, but I had synchronization issues when trying to use Quartz Window Services for that. It didn’t flush in time and I would have had to add sleep(3) :(
-
Ah hm. I take it you’re doing stuff that doesn’t work with -[CALayer drawInContext:]?
-
Yeah, IOSurfaces.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.