No support for any of these
Days since _____

((days since 2000) - ((365) * (number of years))

Weeks:

(round (((((days since 2000) - ((365) * (number of years))) / (7))))

Years: divide by 365
Months: divide by 365 then multiply by 12

Support!

LegendaryTooth wrote:

No support for any of these
Days since _____

((days since 2000) - ((365) * (number of years))

Weeks:

(round (((((days since 2000) - ((365) * (number of years))) / (7))))

Years: divide by 365
Months: divide by 365 then multiply by 12

You aren't considering leap years. If you want to go exact, use ~365.25 instead of 365

LegendaryTooth wrote:

No support for any of these
Days since _____

((days since 2000) - ((365) * (number of years))

Weeks:

(round (((((days since 2000) - ((365) * (number of years))) / (7))))

Years: divide by 365
Months: divide by 365 then multiply by 12

That is really confusing

PATSATDAT wrote:

LegendaryTooth wrote:

No support for any of these
Days since _____

((days since 2000) - ((365) * (number of years))

Weeks:

(round (((((days since 2000) - ((365) * (number of years))) / (7))))

Years: divide by 365
Months: divide by 365 then multiply by 12

That is really confusing

I agree, it would be easier to have a

(days since (2000) :: sensing

The ‘days since 2000’ block is not generally used to figure out the number of days since a certain date. Rather, it is generally used as a method to obtain time which is independent of factors such as when the Scratch project started running or whether a timer has been reset. This is useful for having several timers, having timers which are independent of the ‘timer’ block and synchronizing projects such as multiplayer games.

Source: am user of the ‘days since 2000’ block

support

customhacker wrote:

Abstract- wrote:

([days v] since year[2000]::sensing

Support for the above block instead of “Years since 2000” The default date should be 2000 though.

Dropdown menue options:

Days
Weeks
Months
Years

Yes, this block would be more helpful for clocks.

SUPPORT ^^^^^

jokebookservice1 wrote:

Thelnvoker wrote:

Have you ever used this block?

(days since 2000)

I've rarely heard of anyone ever using it, so I think this block should be changed to a block more customizable.

What should this block be changed to?

I have an idea that instead of the block being a sensor for ‘days since 2000’ you can change the date.

It would look something like this:

(days since [enter date])

(Except blue.)

This way it would count the number of days since the given date.

Thanks!

-@Thelnvoker

Yeah. I support, perhaps a dropdown like this might be better for input validation:

(days since (5) of [January v] of the year [])

Just want to point out that the

(days since 2000)

provides it based on UTC, s you can get smebody's timezone by doing this:

set [timeZone v] to ( (((days since 2000) - ([floor v] of (days since 2000))) * (24)) - (current [hour v]) )

which makes the block useful. But yeah, I support

Agreed.

Duplicate: https://scratch.mit.edu/discuss/topic/58368/

PATSATDAT wrote:

Duplicate: https://scratch.mit.edu/discuss/topic/58368/

Let`s continue discussion there.

It looks like this is a duplicate topic of this one over here so I'll close it to keep the conversation all in one place.

Please use the existing topic in the link above.