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
counter #39
Comments
It seems to be semantically out of scope of this plugin. It would make sense though if the author would change the namespace from |
@DomiBonza at least the math should work both for all real number group, but I have a conditional that clear the timeout if countdown reachs its end, if the former assumption is true so a simple conditional to not do that would do the job for you. @FagnerMartinsBrack I think changing the name is not a option for matter of fallback consistency and historical reasons, but we could provide an alias. |
Thank you for the explanation :) |
Hey mate, I think your request could be implement as a feature in the next release!!! I will reopen this issue until is implemented in the master. Tks |
@hilios I did not meant actually a name change, but an alias as you mentioned (maybe deprecate and use countdown as a property?) |
@hilios It would be awesome :) |
Guys a co-worker did small workaround on my plugin that I think that will be the solution of this issue. Look at PR #52, to take part on the discussion. |
Already implemented at master, the example bellow will count 5 sec from now and then start to count up: var fiveSecAgo = new Date().getTime() + 5000;
$dom.countdown(oneSecAgo, {elapse: true}).on('update.countdown', function(event) {
if (event.elapsed) {
event.strftime('%S passed from end');
} else {
event.strftime('%S till finish');
}
}); |
Hi, is there a way to make the plugin do a normal count instead of a count down?
The text was updated successfully, but these errors were encountered: