Skip to content

Implement allow custom animator range#243

Merged
viddo merged 2 commits intomasterfrom
242-animator-sub-range
Nov 25, 2015
Merged

Implement allow custom animator range#243
viddo merged 2 commits intomasterfrom
242-animator-sub-range

Conversation

@viddo
Copy link
Contributor

@viddo viddo commented Nov 24, 2015

Resolves #242

The steps range have been implicitly [0, steps], to allow setting a custom range I had to make the start+end values explicit. I added a stepsRange concept that holds these values, there's a defaultStepsRange that works as a fallback in case a customStepsRange is not set.

I tried my best to follow existing style and code conventions.

@rochoa can you code review?
cc @javisantana

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's hard to follow when the class is named "AnimatorStepsRange" internally and "StepsRange" here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I'll rename it to AnimatorStepsRange to match the file/definition then

@javisantana
Copy link
Contributor

🇪🇸

viddo added a commit that referenced this pull request Nov 25, 2015
Implement allow custom animator range
@viddo viddo merged commit fd5c3ae into master Nov 25, 2015
@viddo viddo deleted the 242-animator-sub-range branch November 25, 2015 16:02
rochoa added a commit that referenced this pull request Nov 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants