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

Community: is throttling really useful? #50

Open
colthreepv opened this issue Aug 14, 2014 · 2 comments
Open

Community: is throttling really useful? #50

colthreepv opened this issue Aug 14, 2014 · 2 comments
Labels

Comments

@colthreepv
Copy link
Owner

Is throttling on timeupdate (the only recurring event) really useful?

I put it in the first place to limit the Angularjs scope $applies, but it gets triggered few times per second only.
I was thinking to remove it in order to slim the library down and to not overcomplicate it further, leaving throttling to a branch

Write your opinions if you have, thanks

@zappan
Copy link

zappan commented Aug 20, 2014

+1 for the throttle, with some defaults so its configuration could be skipped altogether when not needed

@Martinspire
Copy link

I find it weird its not updating every second as i'm forced to stop everything in between.
I'd like to have a progress-bar implementation so we can get the progress nice an smooth. There is a 0 to 100 percentage from loading, but there isn't for playback. So my progress sliders are really stuttering. Perhaps another value that changes a bit more would be appreciated?

I'll try the trottle-feature tomorrow. Any idea on optimal values?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants