Discuss Scratch
- Discussion Forums
- » Suggestions
- » new block idea
- Jackson2161
-
Scratcher
54 posts
new block idea
the “when time = ___” block that will do something when the time reaches a number
- BulbaLike
-
Scratcher
100+ posts
new block idea
this literally already exists LOL:
when [timer v] > (... ::grey)
- Pixalperfect
-
Scratcher
500+ posts
new block idea
can you explain this block better? like is it this:
wait until timer reaches (120) :: controlin which case you can do
wait until <(timer) = [120]>
- CSwitch
-
Scratcher
100+ posts
new block idea
can you explain this block better? like is it this:Or even better:wait until timer reaches (120) :: controlin which case you can dowait until <(timer) = [120]>
wait until <not <(timer) < (120)>>
- ploppiedog
-
Scratcher
56 posts
new block idea
Sorry, I don't support.
There is a lot of ambiguity on this block. Would it be real world time or time spent in the project?
If it's real world time, it is very confusing, as there is even more ambiguity. Would it be in 12 hour format or 24 hour format? If it was 12 hour format, how would you differentiate AM and PM? If it was in 24 hour format, would it be in 00:00:00 format or 0000 format (if you need to add seconds for the 0000 format, it becomes even more confusing because it could either be 0000:00 or 000000)? Also, there are many time zones that would have to be accounted for. Also, you could do something like this as a workaround:
There is a lot of ambiguity on this block. Would it be real world time or time spent in the project?
If it's real world time, it is very confusing, as there is even more ambiguity. Would it be in 12 hour format or 24 hour format? If it was 12 hour format, how would you differentiate AM and PM? If it was in 24 hour format, would it be in 00:00:00 format or 0000 format (if you need to add seconds for the 0000 format, it becomes even more confusing because it could either be 0000:00 or 000000)? Also, there are many time zones that would have to be accounted for. Also, you could do something like this as a workaround:
when green flag clickedIf the block is based on time spent in the project, it also has an easy workaround that would look something like this:
forever
if <<(current [hour v]) = [8]> and <(current [minute v]) = [26]>> then
logic goes here ::grey
end
when green flag clicked
reset timer
forever
if <(timer) > [120]> then
logic goes here ::grey
end
- medians
-
Scratcher
1000+ posts
new block idea
I think for this, u should just use when timer > () if you're talking about that bc this might break if the timer is not exactly that time
Sorry, I don't support.They probably accidentally put “time” instead of “timer” bc the when time = thing they put in the first post doesn't have multiple inputs though IDK
There is a lot of ambiguity on this block. Would it be real world time or time spent in the project?
If it's real world time, it is very confusing, as there is even more ambiguity. Would it be in 12 hour format or 24 hour format? If it was 12 hour format, how would you differentiate AM and PM? If it was in 24 hour format, would it be in 00:00:00 format or 0000 format (if you need to add seconds for the 0000 format, it becomes even more confusing because it could either be 0000:00 or 000000)? Also, there are many time zones that would have to be accounted for. Also, you could do something like this as a workaround:
- Discussion Forums
- » Suggestions
-
» new block idea