(days since 2000)

(days since(2000)::sensing)//

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

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

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

(days since 2000)

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

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

Abstract- wrote:

Dropdown menue options:

Days
Weeks
Months
Years

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.

(days since(2000)::sensing)//numeric input, default value

TheCode7 wrote:

I support! This is a really cool idea!

Sheep_maker wrote:

Abstract- wrote:

Dropdown menue options:

Days
Weeks
Months
Years

How long is a month? Its length is inconsistent so I don't think it should be a unit of time. Not to mention that an year can be confused as either 365.25 or 365 and 366.

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.

Yes I have used the block, a lot. It's useful for calculating milliseconds or the time zone, an alternative to the timer (and can't be reset!), syncing everyone's values to the same time, etc.

But support for

(days since(2000)::sensing)//numeric input, default value

assuming that 0 = 1BCE, decimals work as normal, and it gives the days until a given year if the year hasn't occurred yet.

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

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

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

And if they put in a future year, like say, 3016, then it would say nothing.

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

dude341 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

And if they put in a future year, like say, 3016, then it would say nothing.

How about:

([days v] [[b]since/until[/b] v] year[2000]::sensing

scratchisthebest wrote:

No support because you can just subtract 365.25 days for every year

Thelnvoker wrote:

scratchisthebest wrote:

No support because you can just subtract 365.25 days for every year

What's the code to do this?

((days since 2000) - ((number of years::grey) * (365.25)))

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

DaSpudLord wrote:

Thelnvoker wrote:

scratchisthebest wrote:

No support because you can just subtract 365.25 days for every year

What's the code to do this?

((days since 2000) - ((number of years::grey) * (365.25)))

ddk44 wrote:

My browser / operating system: ChromeOS 7978.74.0, Chrome 50.0.2661.103, Flash 21.0 (release 0) hahaha

ddk44 wrote:

My browser / operating system: ChromeOS 7978.74.0, Chrome 50.0.2661.103, Flash 21.0 (release 0) hahaha