Digital Workshop

There seems to be a problem with the Date function in Opus script when it reaches a year with 29 days in Feb (a leap year).

It appears that to insist that there are 28 days in Feb 2012 when there should be 29 (or so my outlook calendar says!).

i.e. if you run some script such as:

next_month1 = new Date("Thu Mar 1 2012, 00:00:00");
next_month2 = new Date( 2012, 2, 1);
Debug.trace("next_month1=" + next_month1 + "next_month2=" + next_month2 +"\n")

you get the answer:

Wed Feb 29 2012 00:00:00 in both cases.

note that month=2 is March, as month=0 is Jan, month=1 is Feb, etc.


and...

next_month1 = new Date("Fri Mar 2 2012, 00:00:00");
next_month2 = new Date( 2012, 2, 2);
Debug.trace("next_month1=" + next_month1 + "next_month2=" + next_month2 +"\n")

you get the answer:

Thu Mar 1 2012 00:00:00 in both cases.

i.e. it appears to be always one day behind from then on!

Is there a solution to this anywhere?

/Mark

Opus Pro 06

Yes that's a bug.

However it's only March in a leap year that'll be wrong. If you put in 1st April into your example, it'll be correct.

Dave –

Not to worry!!! According to a documentary I saw this week on the History TV (http://www.history.com) channel, the elaborate calendar systems of the Egyptians, the Mayan civilization, AND the Hopi Indians all end on December 21, 2012 when our Sun is finally located in the exact center of our universe -- called “The Great Alignment”. They also said Nostradamus agrees. After watching this show, I’m convinced, so I wouldn’t worry about fixing the calendar “bug.” We won’t be around.

I’m sure I’m going to get a “pay up sooner” letter from my credit card companies any day now, because they’ll want their money BEFORE the end of time, but that hasn’t stopped me from continuing to charge things. I was even thinking of taking my wife on an elaborate cruise vacation next year (which I’ll charge on my least active credit card) since I won’t be around long enough to pay it off.

But wait! Didn’t a large group of people say the world was going to end when we went from 1999 to 2000? OK, maybe (to be safe) you should fix the calendar bug – just in case time doesn’t end on December 21, 2012.

(Can you tell business is slow, and I've got WAY too much time on my hands?)

Hi Fred,

Did they give a time? It's just I've got tea with the Queen booked for 11am GMT on that day and I'd hate to miss the appointment - seems rude

As for the bug, my money is on all those unlucky sods born on the 29th February conspiring to make the day last longer.

On a slightly more serious note Mark, if it's necessary to use dates that far in advanced, then I'd create a new function or method and pass the new Date parameters to that instead. A leap year is normally any year dividable by four, the next exception being not for another 91years, so you could use this function to ascertain whether the date is march in a leap year, offset by one day and create the new Date object from this data.

Okay, it's royal pain, but less drastic than the end of world.

Is it Friday yet?

Mack

When we were younger, we certainly did not look out that far in advance. Probably we only looked ahead a week, and 'get a date' meant something entirely different from the current thread. Now look where we've arrived! (Mac excepted... who has a date with the Queen).

Have you checked if you get same problem using Roman dates? mmxxii/iii/oi ?