There is this block that exists which is the days since 2000
And other people suggested a days since ____ block.


However, I haven't seen anyone suggest a days until block.
Benefits:
Countdown to _______!
I used SD 2015 in this example. There is workarounds, but I want it easier for begginers to try.
The block:
(If you set the time to 0, it will report only the whole number

<days until (May v) - (9 v) - (2015) - (0 v):(0 v) (PM v) :: sensing> 

Support!

That might be nice, so support, but one question: What if it is after the date posted? I would suggest something like this, since it would also count days from:

<time until (May v) - (9 v) - (2015) - (7 v):(47 v) (PM v) :: sensing> 
// (This uses drop down lists so that you can't make impossible date\times)

PS. Just learned how to make blocks look like what I want them to look like in this topic: https://scratch-mit-edu.ezproxy.canberra.edu.au/discuss/topic/55586/

Apparently my old signature was lost::custom hat
Oh well, I guess this will do ::custom cap

georgeskey wrote:

That might be nice, so support, but one question: What if it is after the date posted? I would suggest something like this, since it would also count days from:

<time until (May v) - (9 v) - (2015) - (7 v):(47 v) (PM v) :: sensing> 
// (This uses drop down lists so that you can't make impossible date\times)

PS. Just learned how to make blocks look like what I want them to look like in this topic: https://scratch-mit-edu.ezproxy.canberra.edu.au/discuss/topic/55586/

Nice

georgeskey wrote:

That might be nice, so support, but one question: What if it is after the date posted? I would suggest something like this, since it would also count days from:

<time until (May v) - (9 v) - (2015) - (7 v):(47 v) (PM v) :: sensing> 
// (This uses drop down lists so that you can't make impossible date\times)

PS. Just learned how to make blocks look like what I want them to look like in this topic: https://scratch-mit-edu.ezproxy.canberra.edu.au/discuss/topic/55586/

It will go negative, like if I write Sunday May 9, it will report -1

Support. The way you have done it still allows impossible times though, so something would have to be done about that. Also, if it has time (which isn't really needed) it should be 24 hours, because it will have one less input and be easier to work with.

support!

say [who you gonna follow...]
say [Charmind!]
click (follow Charmind:: sensing)::control

No support. Just use

((days between this date and 2000) - (days since 2000))

TheHockeyist wrote:

No support. Just use

((days between this date and 2000) - (days since 2000))

Days since 2000 gives you stuff like 2435.234 (making up). I want it to be stuff like 23345

Support. Why isn't there this already?

when [chromometer altimeter v] = [5th length v] and [7th length v] with a [gap v] of (17) ::events hat
forge [chromometer v] altimeter until < (speed) = (velocity)> ::control cstart
	switch places with (759 v) altimeters with value of (speed) ::looks
	control [altimeter 1 v] at time (10):(17):(58) ::control
end
initialize sequence (24) so [object 3 v] moves to x (156) y (231) ::control
reveal [final answer v] and stop running this script ::events cap

cwkethan1508 wrote:

TheHockeyist wrote:

No support. Just use

((days between this date and 2000) - (days since 2000))

Days since 2000 gives you stuff like 2435.234 (making up). I want it to be stuff like 23345

If you only want the whole number of days, use

([floor v] of (days since 2000))

Dates are written differently throughout different countries - some day/month/year, some month/day/year, etc. Unless it's easy to tell which is which:

([days v] until day:[12th v] month:[May v] year:[2015 v]::sensing

it could cause a lot of confusion, and as Scratch is based in America we'll probably all have to use month/day/year which makes zero sense.
Additionally, people could still make impossible dates with a dropdown in - the 31st of Feburary doesn't work. Unless 31st Feburary = 3rd March or it rounds down to the highest date for the month, but then it has to include leap years…
As this could get too complex and there is already a viable workaround, I don't support.

Prinseskat wrote:

Dates are written differently throughout different countries - some day/month/year, some month/day/year, etc. Unless it's easy to tell which is which:

([days v] until day:[12th v] month:[May v] year:[2015 v]::sensing

it could cause a lot of confusion, and as Scratch is based in America we'll probably all have to use month/day/year which makes zero sense.
Additionally, people could still make impossible dates with a dropdown in - the 31st of Feburary doesn't work. Unless 31st Feburary = 3rd March or it rounds down to the highest date for the month, but then it has to include leap years…
As this could get too complex and there is already a viable workaround, I don't support.

I would prefer it to have number inputs, that way you could drop reporters into the slots.
For impossible dates, it would probably either roll over or cap them, but as long as it was consistent it wouldn't matter too much.
Labelling the inputs is a good idea - I think it should be year-month-day since that is the international standard.

cwkethan1508 wrote:

TheHockeyist wrote:

No support. Just use

((days between this date and 2000) - (days since 2000))

Days since 2000 gives you stuff like 2435.234 (making up). I want it to be stuff like 23345

You can use

(round ((days between this date and 2000) - (days since 2000)))

U^ｪ^U::motion//This is Blocky. He lives in my signature. He is a trained attack block. He protects my siggy from kumquats.

I want this to make it easier, with NO WORKAROUNDS. Also, what if someone is too lazy to calculate?

Prinseskat wrote:

Dates are written differently throughout different countries - some day/month/year, some month/day/year, etc. Unless it's easy to tell which is which:

([days v] until day:[12th v] month:[May v] year:[2015 v]::sensing

it could cause a lot of confusion, and as Scratch is based in America we'll probably all have to use month/day/year which makes zero sense.
Additionally, people could still make impossible dates with a dropdown in - the 31st of Feburary doesn't work. Unless 31st Feburary = 3rd March or it rounds down to the highest date for the month, but then it has to include leap years…
As this could get too complex and there is already a viable workaround, I don't support.

The dates you can choose depends on the Month.
Same with this blocks

(current [date v])

That talks about dates. So, its like the same confusion for people out of america

cwkethan1508 wrote:

The dates you can choose depends on the Month.
Same with this blocks

(current [date v])

That talks about dates. So, its like the same confusion for people out of america

Current date seems to give you the nth number of the month. I don't know about dropdowns changing - if you were able to drop a variable in (or force one in with the JSON code) a slot, you could still make an impossible date.

stickfiregames wrote:

I would prefer it to have number inputs, that way you could drop reporters into the slots.
For impossible dates, it would probably either roll over or cap them, but as long as it was consistent it wouldn't matter too much.
Labelling the inputs is a good idea - I think it should be year-month-day since that is the international standard.

Some dropdowns you can insert variables in, and some you can type a number in. I suppose some workaround for impossible dates would be good them, as no matter what you can still get one.

cwkethan1508 wrote:

I want this to make it easier, with NO WORKAROUNDS. Also, what if someone is too lazy to calculate?

“I'm too lazy” is not an excuse for a new block to be made instead of using a workaround.

+1

DaSpudLord wrote:

cwkethan1508 wrote:

TheHockeyist wrote:

No support. Just use

((days between this date and 2000) - (days since 2000))

Days since 2000 gives you stuff like 2435.234 (making up). I want it to be stuff like 23345

You can use

(round ((days between this date and 2000) - (days since 2000)))

Using that workaround will cause it to go to the next day at 12:00pm.

([floor v] of (9))

would be a better idea.

+1
Edit: -1, no support.