Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a "Start at measure {n}" feature #540

Open
islemaster opened this issue Nov 30, 2018 · 0 comments
Open

Add a "Start at measure {n}" feature #540

islemaster opened this issue Nov 30, 2018 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@islemaster
Copy link
Contributor

The problem: Iterating on the last part of a dance party project (near the end of the song) can be very, very slow because you have to listen through the first part of the song in real-time every time you want to test your changes.

Proposed solution: Add a debug feature for starting playback at a particular measure.

Considerations:

Dance Party code is highly stateful (creating dancers, setting effects, etc) so instead of only executing student code that occurs after measure n we probably need to "fast-forward" through all of their code up to that point, executing events before measure n sequentially and as fast as possible. (This roughly mirrors the behavior of sinon's fake timers tick() method.)

@islemaster islemaster added the enhancement New feature or request label Nov 30, 2018
@ryansloan ryansloan added this to the Post HOC milestone Dec 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants