Skip to content

Releases: wimbarelds/TimeCircles

Bug fixes and functionality

04 Feb 18:23
Compare
Choose a tag to compare

Fixed a bug with setting count_past_zero giving errors.

Added functionality that lets you set what time circles views as the "total duration".

By default, the total duration is 1 year (or more accurately, 365 days), however you can now also set it to a month (meaning the "Days" timer would be roughly half full at 15 days).

By setting it to "Auto", TimeCircles will simply look at which values you're showing- and pick something bigger than your biggest unit.

Other available settings are: "Years", "Months", "Days", "Hours", "Minutes".

You can also give this variable a numeric value (in seconds). So, if for example you're only showing the 'Seconds' timer, you can set total_duration to 100 (Or any other value).

Simply do:
$("Countdown").TimeCircles({ total_duration: "Months" });

To use this setting.

Bug fixes

30 Jan 13:16
Compare
Choose a tag to compare

Fixed a bug in the destroy feature and changed a behavior when the biggest units are not being shown.

plugins.jquery.com update

20 Jan 00:02
Compare
Choose a tag to compare

plugins.jquery.com did not recognize the last update. Only pushing a new release so that it gets updated there. No other reason.

New functionality

19 Jan 19:35
Compare
Choose a tag to compare

Added functions:

  • .restart()
  • .rebuild()
  • .getTime()

Added extra parameter to addListener, type. Should be either "all" or "visible", default = "visible".
If set to all, will also broadcast changes of values that are not being shown. See issue #12

1.0.5

10 Jan 15:39
Compare
Choose a tag to compare

Resolved issues:

addListener fix

10 Jan 14:00
Compare
Choose a tag to compare

Previously, the addListener function would give a total value as third parameter to the callback. The total value however was an absolute value (Math.abs). This is no longer the case.

Bug fixes

09 Jan 15:58
Compare
Choose a tag to compare

Bug fixes:

  • TimeCircles incorrectly read width and height as 0 if it was hidden. This is fixed now.
  • Avoid Date.parse when given a date string as formatted in documentation. Date.parse does not use local time and can be inconsistent. Kept using it as fallback, so that strings like: "Thu Jan 09 2014 16:55:47 GMT+0100" can still be used.

1.0.2

05 Jan 16:09
Compare
Choose a tag to compare

Fixed Date.parse for safari and flickering issue when count_past_zero was set to false.