You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: