topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • October 22, 2018, 02:38 AM
  • Proudly celebrating 13 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Calendar Week 52 instead of 1  (Read 1922 times)

melaw

  • Participant
  • Joined in 2018
  • *
  • default avatar
  • Posts: 3
    • View Profile
    • Donate to Member
Calendar Week 52 instead of 1
« on: January 04, 2018, 03:00 AM »
Hello folks,
title says it all. I use the calendar week format Wi and it shows the current calendar week to be 52,
while it is of course January 4th and therefore calendar week 1.

Using Wu instead of Wi does give my week 1, however after looking up ISO 8601 I have
to report this to be a bug in T-clock.

BR
A user

WhiteTigX

  • Moderator
  • Joined in 2013
  • *****
  • Posts: 156
    • View Profile
    • Donate to Member
Re: Calendar Week 52 instead of 1
« Reply #1 on: January 04, 2018, 07:38 AM »
Related issue: #128
My latest release of T-Clock Redux can always be found here, on my Github releases page

melaw

  • Participant
  • Joined in 2018
  • *
  • default avatar
  • Posts: 3
    • View Profile
    • Donate to Member
Re: Calendar Week 52 instead of 1
« Reply #2 on: January 04, 2018, 07:48 AM »
Much appreciated! Still possible to fix it before week 01/2018 ;-)

WhiteTigX

  • Moderator
  • Joined in 2013
  • *****
  • Posts: 156
    • View Profile
    • Donate to Member
Re: Calendar Week 52 instead of 1
« Reply #3 on: January 28, 2018, 03:12 PM »
Well, I didn't fix it in time.. (not at all) but it's done now at long last: v2.4.4
My latest release of T-Clock Redux can always be found here, on my Github releases page

melaw

  • Participant
  • Joined in 2018
  • *
  • default avatar
  • Posts: 3
    • View Profile
    • Donate to Member
Re: Calendar Week 52 instead of 1
« Reply #4 on: January 29, 2018, 03:03 AM »
Well, I didn't fix it in time.. (not at all) but it's done now at long last: v2.4.4

Working perfectly, thanks!