helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

helloyowuzzup wrote:

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

That's also true, but that, as others have said, brings up the problem of time zones.

Why?

Because if you want to set it to do something at a set time, you'd have to use a time zone converter to set it to Massachusetts time. But newer scratchers wouldn't know that, and it could easily get very confusing.

No you won't. What's the point of doing that anyway? Besides, that's not the ONLY thing the block does.

Well, what if I want to make a time-limited cloud poll? Maybe if I want to code a special event into a game or something? A timer counting down until something important happens?

You can use a cloud variable.

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

helloyowuzzup wrote:

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

That's also true, but that, as others have said, brings up the problem of time zones.

Why?

Because if you want to set it to do something at a set time, you'd have to use a time zone converter to set it to Massachusetts time. But newer scratchers wouldn't know that, and it could easily get very confusing.

No you won't. What's the point of doing that anyway? Besides, that's not the ONLY thing the block does.

Well, what if I want to make a time-limited cloud poll? Maybe if I want to code a special event into a game or something? A timer counting down until something important happens?

You can use a cloud variable.

How would I do that without leaving the project on in my browser for every second of every day?

during a random moment :: events hat

when it's ():():() [AM v] :: events hat

(current [time v])

Scratchifier wrote:

during a random moment :: events hat

How would it define how random? The work around is actually pretty simple.

when it's ():():() [AM v] :: events hat

Hmm, could be useful to make personal alarm clocks! But other than that, I don't see much of a use without complicating things a bit… Just make it UTC-0 for the timezone, and that could work. (Although also a little bubble next to that, considering that I don't even know when that is. XD)

(current [time v])

Yeah, that could be good. Same timezone as previous block, and I'd like it…

So basically, support for second two if you change a few things around.

lalala3 wrote:

Diamond_Projects wrote:

Ok, ok, now, I don't think a New Scratcher will understand

when green flag clicked
forever
    ...
wait (pick random (... :: grey) to (... :: grey)) secs
end

Or

when green flag clicked
forever
    
if <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)> then
    ...
wait until <not <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)>>
end

end

Not if it's too complicated. That's why I think we should have these:

during a random moment :: events hat
when it's ():():() [AM v] :: events hat
(current [time v])

They're a lot simpler

It's not really all that complicated. In terms of complexity, it's at most around the level of doing arithmetic with multiple-digit numbers. It's just mindlessly following an easy step-by-step process that pretty much everyone over the age of 5 should know how to do, but gives off the illusion of complexity because people find it hard to grasp the difference between “tedious” and “difficult”. If someone can't figure out something as straightforward as that, then s/he needs to develop the critical thinking skills to do so. Programming, whether in Scratch or any other language, is all about this stuff, from top to bottom.

Diamond_Projects wrote:

during a random moment :: events hat // too ambiguous/vague
when it's ():():() [AM v] :: events hat // use if <(current time) = ( )> instead
(current [time v]) // support, it would be easier than stringing together sensing blocks
// current time should be based on local time since all other current blocks are

(Scratch time [hour v] :: sensing)
(UTC [hour v] :: sensing) // I would prefer this to Scratch time
(current [hour v] in UTC ＋(0 v) :: sensing) // This would have the most flexibility but might confuse people

-12
-11
-10 Hawaii
-9  Alaska
-8  Pacific
...

(current [time v])

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

Ok, ok, now, I don't think a New Scratcher will understand

when green flag clicked
forever
    ...
wait (pick random (... :: grey) to (... :: grey)) secs
end

Or

when green flag clicked
forever
    
if <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)> then
    ...
wait until <not <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)>>
end

end

Not if it's too complicated. That's why I think we should have these:

during a random moment :: events hat
when it's ():():() [AM v] :: events hat
(current [time v])

They're a lot simpler

It's not really all that complicated. In terms of complexity, it's at most around the level of doing arithmetic with multiple-digit numbers. It's just mindlessly following an easy step-by-step process that pretty much everyone over the age of 5 should know how to do, but gives off the illusion of complexity because people find it hard to grasp the difference between “tedious” and “difficult”. If someone can't figure out something as straightforward as that, then s/he needs to develop the critical thinking skills to do so. Programming, whether in Scratch or any other language, is all about this stuff, from top to bottom.

Ok, too overwhelming.

TheHockeyist wrote:

-12
-11
-10 Hawaii
-9  Alaska
-8  Pacific
...

One problem. Daylight Saving Time.

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

Ok, ok, now, I don't think a New Scratcher will understand

when green flag clicked
forever
    ...
wait (pick random (... :: grey) to (... :: grey)) secs
end

Or

when green flag clicked
forever
    
if <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)> then
    ...
wait until <not <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)>>
end

end

Not if it's too complicated. That's why I think we should have these:

during a random moment :: events hat
when it's ():():() [AM v] :: events hat
(current [time v])

They're a lot simpler

It's not really all that complicated. In terms of complexity, it's at most around the level of doing arithmetic with multiple-digit numbers. It's just mindlessly following an easy step-by-step process that pretty much everyone over the age of 5 should know how to do, but gives off the illusion of complexity because people find it hard to grasp the difference between “tedious” and “difficult”. If someone can't figure out something as straightforward as that, then s/he needs to develop the critical thinking skills to do so. Programming, whether in Scratch or any other language, is all about this stuff, from top to bottom.

Ok, too overwhelming.

Not really. Scratch just makes it look messy.

stickfiregames wrote:

No support for the first two, but support for current time

Diamond_Projects wrote:

during a random moment :: events hat // too ambiguous/vague
when it's ():():() [AM v] :: events hat // use if <(current time) = ( )> instead
(current [time v]) // support, it would be easier than stringing together sensing blocks
// current time should be based on local time since all other current blocks are

I also support having global time blocks. Here are some ideas:

(Scratch time [hour v] :: sensing)
(UTC [hour v] :: sensing) // I would prefer this to Scratch time
(current [hour v] in UTC ＋(0 v) :: sensing) // This would have the most flexibility but might confuse people

The dropdown for the last one would have numbers and descriptions, like the point in direction block:

-12
-11
-10 Hawaii
-9  Alaska
-8  Pacific
...

if <key [ v] pressed?> then
    
end

when [ v] key pressed

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

Ok, ok, now, I don't think a New Scratcher will understand

when green flag clicked
forever
    ...
wait (pick random (... :: grey) to (... :: grey)) secs
end

Or

when green flag clicked
forever
    
if <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)> then
    ...
wait until <not <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)>>
end

end

Not if it's too complicated. That's why I think we should have these:

during a random moment :: events hat
when it's ():():() [AM v] :: events hat
(current [time v])

They're a lot simpler

It's not really all that complicated. In terms of complexity, it's at most around the level of doing arithmetic with multiple-digit numbers. It's just mindlessly following an easy step-by-step process that pretty much everyone over the age of 5 should know how to do, but gives off the illusion of complexity because people find it hard to grasp the difference between “tedious” and “difficult”. If someone can't figure out something as straightforward as that, then s/he needs to develop the critical thinking skills to do so. Programming, whether in Scratch or any other language, is all about this stuff, from top to bottom.

Ok, too overwhelming.

Not really. Scratch just makes it look messy.

Okay, too messy.

run 3d game.

Braeden5454 wrote:

Eh, seems unessisary to add 3 new blocks simply because somebody doesn't know how to do things. Its kinda like making a block that says:

run 3d game.

if on edge, bounce

Diamond_Projects wrote:

TheHockeyist wrote:

-12
-11
-10 Hawaii
-9  Alaska
-8  Pacific
...

One problem. Daylight Saving Time.

Uses your computer's time.

TheHockeyist wrote:

-12
-11
-10 Hawaii
-9  Alaska
-8  Pacific
...

One problem. Daylight Saving Time.

stickfiregames wrote:

Diamond_Projects wrote:

TheHockeyist wrote:

-12
-11
-10 Hawaii
-9  Alaska
-8  Pacific
...

One problem. Daylight Saving Time.

Uses your computer's time.

No, it uses the server time, that was the point of my suggestion.

TheHockeyist wrote:

-12
-11
-10 Hawaii
-9  Alaska
-8  Pacific
...

One problem. Daylight Saving Time.

That might be an issue for listing the time zones on the dropdown. The actual value of, say, UTC-12, wouldn't be affected by that.

Diamond_Projects wrote:

MY suggestion was the computer's time.

Diamond_Projects wrote:

Braeden5454 wrote:

Eh, seems unessisary to add 3 new blocks simply because somebody doesn't know how to do things. Its kinda like making a block that says:

run 3d game.

Eh, seems unessisary to add a new block simply because somebody doesn't know how to do things. Its kinda like making a block that says:

if on edge, bounce