Discuss Scratch
- unknown2467
-
100+ posts
when variable changes
<[variable v] changing?::variables>Is basically as ambiguous as
[message v] broadcasted?::events boolean
#10So you mean the boolean will return the timestamp when it was true?
I support!
However, the
<[variable v] changing?::variables>
Boolean block could be turned into this to make a little more sense:<When [variable v] changes::variables>
This way, it would be easier to tell what it means!
Last edited by unknown2467 (Feb. 6, 2025 17:08:31)
- AvidOsirianGuy
-
100+ posts
when variable changes
are some of these ideas rejected or dupes? quote me if so.
- jmb1293634
-
100+ posts
when variable changes
I admit that the boolean is a little ambiguous it would be true either if the variable had changed since the last time it had been called or if the variable had been changed in the last frame<[variable v] changing?::variables>Is basically as ambiguous as[message v] broadcasted?::events boolean#10So you mean the boolean will return the timestamp when it was true?
I support!
However, the
<[variable v] changing?::variables>
Boolean block could be turned into this to make a little more sense:<When [variable v] changes::variables>
This way, it would be easier to tell what it means!
- jmdzti_0-0
-
500+ posts
when variable changes
< is changing> is too ambiguous.
when [timer v] > ((timer) + <(foo) = (bar)>)
set [bar v] to (foo)
...::grey
repeat until <not <(foo) = (bar)>
...::grey
end
set [foo v] to (bar)
wait until <not <(foo) = (bar)>>
set [foo v] to (bar)
...::grey