Skip to content

/ teletype

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

Jump to bottom

metro rate not updated after INIT.SCENE #174

Closed
scanner-darkly opened this issue Jan 3, 2019 · 0 comments
Closed

metro rate not updated after INIT.SCENE #174

scanner-darkly opened this issue Jan 3, 2019 · 0 comments

Comments

@scanner-darkly
Copy link
Member

@scanner-darkly scanner-darkly commented Jan 3, 2019 •
edited

Please describe the bug.

INIT.SCENE doesn't reinitialize metro rate. same for INIT and INIT.DATA

Please include the hash displayed at startup and the release of the software (e.g. "Teletype v2.0.1 5f838c9")

1b53ffe

What steps are required to reproduce the bug?

set metro rate to something other than 1000
execute INIT.SCENE
check metro rate - it should return 1000 but the actual rate will be whatever you set it to before INIT.SCENE
scanner-darkly added a commit to scanner-darkly/teletype that referenced this issue Jan 3, 2019
@scanner-darkly
fixes monome#174
31351a6
@scanner-darkly scanner-darkly mentioned this issue Jan 3, 2019
Merged
1 of 3 tasks complete
scanner-darkly added a commit that referenced this issue Jan 3, 2019
@scanner-darkly
Dev3 (#175)
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.
GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Loading status checks…
a235649 
fix for issue #174
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@scanner-darkly