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

displayPeriod as a HyPerCol parameter made available to all objects #93

Open
peteschultz opened this issue Jul 20, 2016 · 1 comment
Open
Assignees

Comments

@peteschultz
Copy link
Contributor

displayPeriod started out as a Movie parameter, and it is still only defined for Movie, MoviePvp, and Patterns (the last of which hasn't been used in quite a while). However, it is very common for objects to trigger off of these layers, with more than one possible triggering behavior, creating difficult-to-manage interdependencies.

Accordingly, I'm thinking that it would make sense to have displayPeriod be a HyPerCol parameter, and pass that parameter (or perhaps the time to next display period) as an argument to updateState. This would make the most common reason for triggering unnecessary.

Thoughts?

@austinthresher
Copy link
Member

I like this idea a lot. The only potential issue I can think of is Gar's taps- they might not work with a setup like this.

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

No branches or pull requests

5 participants