Closed domhofmann closed 13 years ago
We should use this an opportunity to make a decision regarding overloads as well. Moving forward, will we support multiple versions of our methods or would we rather have developers passing in nil
and NULL
?
I've added basic support for this in the 0.2-dev branch. For example:
[PRTween tween:testView property:@"alpha" from:1 to:0 duration:3];
You can also directly tween values. Suppose you're developing a game that has a scrollPosition
CGFloat.
[PRTween tween:&scrollPosition from:0 to:20 duration:3];
Merged into master.
There will be times that developers simply want to tween some value from A to B without writing a lot of code. In these cases, it seems like we should support something similar to the following.
We could support these "overloads":
We should also support non-relative tweens: