more timer blocks

supercroissants

I_wantasheep wrote:
ever heard of
forever
change [timer1 v] by (1)
wait (1) seconds

we shouldn't have to make variables to use blocks as simple as these

NutOfCoco

supercroissants wrote:
I_wantasheep wrote:
ever heard of
forever
change [timer1 v] by (1)
wait (1) seconds
we shouldn't have to make variables to use blocks as simple as these

Sorry to break this to you, but a timer is a variable.

supercroissants

NutOfCoco wrote:
supercroissants wrote:
I_wantasheep wrote:
ever heard of
forever
change [timer1 v] by (1)
wait (1) seconds
we shouldn't have to make variables to use blocks as simple as these
Sorry to break this to you, but a timer is a variable.

sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would be

you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer

if we removed every block that had a workaround nobody would use the site

NutOfCoco

supercroissants wrote:
NutOfCoco wrote:
supercroissants wrote:
I_wantasheep wrote:
ever heard of
forever
change [timer1 v] by (1)
wait (1) seconds
we shouldn't have to make variables to use blocks as simple as these
Sorry to break this to you, but a timer is a variable.
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would be

you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer

if we removed every block that had a workaround nobody would use the site

Sorry to break it to you, but a constant is a variable that does not change, a timer's whole purpose is to change, and most people when giving a workaround are giving it to the person so that person can implement use the suggested block before the suggestion is added (or never).

supercroissants

NutOfCoco wrote:
supercroissants wrote:
NutOfCoco wrote:
supercroissants wrote:
I_wantasheep wrote:
ever heard of
forever
change [timer1 v] by (1)
wait (1) seconds
we shouldn't have to make variables to use blocks as simple as these
Sorry to break this to you, but a timer is a variable.
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would be

you don't make it, you don't have to do anything to make it appear, it is a constant
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer

if we removed every block that had a workaround nobody would use the site
Sorry to break it to you, but a constant is a variable that does not change, a timer's whole purpose is to change, and most people when giving a workaround are giving it to the person so that person can implement use the suggested block before the suggestion is added (or never).

sorry to break it to you, I know that!
I said constant in the sense that it will always be a thing in scratch projects.

and the message that we're all quoting is in a tone that suggests “hey, here's a workaround. this suggestion bad!”

workarounds and overprotective people will be the death of this forum

r3hehehehehhe

supercroissants wrote:
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would be

you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer

if we removed every block that had a workaround nobody would use the site

i agree with you, it's like saying we don't need

<<boolean::grey> and <boolean::grey>>

we can use

<<<boolean::grey> = [true]> = <<boolean::grey> = [true]>>

NutOfCoco

r3hehehehehhe wrote:
supercroissants wrote:
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would be

you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer

if we removed every block that had a workaround nobody would use the site
i agree with you, it's like saying we don't need
<<boolean::grey> and <boolean::grey>>
we can use
<<<boolean::grey> = [true]> = <<boolean::grey> = [true]>>

That workaround doesn't work, it is also true for two false values.

robloxnoob27

NutOfCoco wrote:
r3hehehehehhe wrote:
supercroissants wrote:
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would be

you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer

if we removed every block that had a workaround nobody would use the site
i agree with you, it's like saying we don't need
<<boolean::grey> and <boolean::grey>>
we can use
<<<boolean::grey> = [true]> = <<boolean::grey> = [true]>>
That workaround doesn't work, it is also true for two false values.

<not <<not <boolean::grey>> or <not <boolean::grey>>>

NutOfCoco

supercroissants wrote:
NutOfCoco wrote:
supercroissants wrote:
NutOfCoco wrote:
supercroissants wrote:
I_wantasheep wrote:
ever heard of
forever
change [timer1 v] by (1)
wait (1) seconds
we shouldn't have to make variables to use blocks as simple as these
Sorry to break this to you, but a timer is a variable.
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would be

you don't make it, you don't have to do anything to make it appear, it is a constant
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer

if we removed every block that had a workaround nobody would use the site
Sorry to break it to you, but a constant is a variable that does not change, a timer's whole purpose is to change, and most people when giving a workaround are giving it to the person so that person can implement use the suggested block before the suggestion is added (or never).
and the message that we're all quoting is in a tone that suggests “hey, here's a workaround. this suggestion bad!”

What about mine?

Last edited by NutOfCoco (Yesterday 04:43:00)

robloxnoob27

sit3

robloxnoob27

17 block workaround:

define timer (type) (start time)
set [timer v] to (start time)
reset timer
repeat until <(timer::variables) < [0]>
set [timer v] to ((start time)-((((2)*<(type)=[countdown]>)-[1])*(timer)))
end
set [timer v] to [0]

robloxnoob27

sit3

Toodchop

We are the coughing babies near a hydrogen bomb 100 feet away

I'm not into new timer blocks. But anyways, I support this idea.

Last edited by Toodchop (Today 10:19:42)

supercroissants

NutOfCoco wrote:
supercroissants wrote:
NutOfCoco wrote:
supercroissants wrote:
NutOfCoco wrote:
supercroissants wrote:
I_wantasheep wrote:
ever heard of
forever
change [timer1 v] by (1)
wait (1) seconds
we shouldn't have to make variables to use blocks as simple as these
Sorry to break this to you, but a timer is a variable.
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would be

you don't make it, you don't have to do anything to make it appear, it is a constant
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer

if we removed every block that had a workaround nobody would use the site
Sorry to break it to you, but a constant is a variable that does not change, a timer's whole purpose is to change, and most people when giving a workaround are giving it to the person so that person can implement use the suggested block before the suggestion is added (or never).
and the message that we're all quoting is in a tone that suggests “hey, here's a workaround. this suggestion bad!”
What about mine?

annoyingly confusing and complicated

NutOfCoco

supercroissants wrote:
NutOfCoco wrote:
supercroissants wrote:
NutOfCoco wrote:
supercroissants wrote:
NutOfCoco wrote:
supercroissants wrote:
I_wantasheep wrote:
ever heard of
forever
change [timer1 v] by (1)
wait (1) seconds
we shouldn't have to make variables to use blocks as simple as these
Sorry to break this to you, but a timer is a variable.
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would be

you don't make it, you don't have to do anything to make it appear, it is a constant
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer

if we removed every block that had a workaround nobody would use the site
Sorry to break it to you, but a constant is a variable that does not change, a timer's whole purpose is to change, and most people when giving a workaround are giving it to the person so that person can implement use the suggested block before the suggestion is added (or never).
and the message that we're all quoting is in a tone that suggests “hey, here's a workaround. this suggestion bad!”
What about mine?
annoyingly confusing and complicated

You are not good at understanding code then, it is quite simple.

r3hehehehehhe

support
maybe there could be an

(::ring)add timer +(::ring)::ring grey

button and

(::ring)remove timer -(::ring)::ring grey

block, and there's

(timer [1 v]::sensing)

(timer [2 v]::sensing)

(timer [3 v]::sensing)

and also

reset timer [1 v]::sensing

Last edited by r3hehehehehhe (Today 16:28:28)

r3hehehehehhe

NutOfCoco wrote:
You are not good at understanding code then, it is quite simple.

a toddler could learn algebra quicker than that, it's just easier to have prebuilt timers

supercroissants

NutOfCoco wrote:
You are not good at understanding code then, it is quite simple.

or maybe i dont want to waste my time using a disgusting workaround requiring 2 variables, 3 lists, and 2 custom blocks when the ST could just add this in an hour

NutOfCoco

supercroissants wrote:
NutOfCoco wrote:
You are not good at understanding code then, it is quite simple.
or maybe i dont want to waste my time using a disgusting workaround requiring 2 variables, 3 lists, and 2 custom blocks when the ST could just add this in an hour

Here is a more efficient one then, without one feature (that didn't wasn't even remotely required):

define add timer (direction) (start) //direction instead of type, uses direct values (1 for stopwatch, -1 for countdown)
add ((timer) - ((start) * (direction))) to [timerStart v]
add (direction) to [timerDir v]

define timer (index)
set [timer v] to ((item (index) of [timerDir v]) * ((timer) - (item (index) of [timerStart v])))

Though I can't believe someone would like scratch if they don't want to code.

Last edited by NutOfCoco (Today 22:27:59)

Discuss Scratch