Note that there are some explanatory texts on larger screens.

plurals
  1. USgroundhog
    primarykey
    data
    text
    plurals
    1. COAgain, I would say it should be a class that has a NSManagedObject, not is a NSManagedObject. If the decorator is not one, then it shouldn't inherit that class (all the way down the class hierarchy). What you are essentially saying here is that you want some of the descendants to be like a NSManagedObject and others to not. That means those descendants should behave that way not the base class. If you used a protocol, you would have one protocol and four implementations of that protocol. The ones that are NSManagedObjects would inherit that class.
      singulars
    2. COActually, this is incorrect. CAAnimation has a transaction model and transactions do nest, so it queues all the animations with different start times into the same animation transaction . Without doing it this way the performance is even worse due to all the animation scheduling overhead. I've tried doing each pass individually and letting each animation run in it's own transaction independently, and it's got all sorts of issues. NSTimers lead to animation phase mismatches due to minor scheduling jitter. animationsDidFinish ends up not helping except for an additional selector call.
      singulars
    3. CO@chrispix - side question, is there a way to automatically sweep all code into the test target without having to explicitly add them each time to create a new class?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload