Discuss Scratch
- Discussion Forums
- » Suggestions
- » Days since:
- DerpTrollWizrd
-
Scratcher
11 posts
Days since:
(days since ())
And also would be cool:
show timer
hide timer
- rasmusolle
-
Scratcher
100+ posts
Days since:
No support
The show and hide has a workaround though
The show and hide has a workaround though
Last edited by rasmusolle (June 4, 2016 12:15:00)
- redgreenandblue
-
Scratcher
100+ posts
Days since:
This is a duplicate but I support! Also, you should look at this: https://scratch.mit.edu/discuss/topic/201279/?page=2#post-2018629 It has the rules to block suggesting. (it isn't a sticky but these are still real rules)
- Lythium
-
Scratcher
1000+ posts
Days since:
This is a duplicate but I support! Also, you should look at this: https://scratch.mit.edu/discuss/topic/201279/?page=2#post-2018629 It has the rules to block suggesting. (it isn't a sticky but these are still real rules)Since these are only 3 blocks, I guess it's fine.
- redgreenandblue
-
Scratcher
100+ posts
Days since:
Yes, but they would be in different categories.This is a duplicate but I support! Also, you should look at this: https://scratch.mit.edu/discuss/topic/201279/?page=2#post-2018629 It has the rules to block suggesting. (it isn't a sticky but these are still real rules)Since these are only 3 blocks, I guess it's fine.
(days since ()::operators)If they were in the same category then that would be fine.
show timer::sensing
hide timer::sensing
(My 100th Post!)
Last edited by redgreenandblue (June 1, 2016 16:29:11)
- redgreenandblue
-
Scratcher
100+ posts
Days since:
I didn't mean to quote I meant to edit 

Last edited by redgreenandblue (June 1, 2016 16:28:54)
- Lythium
-
Scratcher
1000+ posts
Days since:
All of them would be in sensing.Yes, but they would be in different categories.This is a duplicate but I support! Also, you should look at this: https://scratch.mit.edu/discuss/topic/201279/?page=2#post-2018629 It has the rules to block suggesting. (it isn't a sticky but these are still real rules)Since these are only 3 blocks, I guess it's fine.(days since ()::operators)If they were in the same category then that would be fine.
show timer::sensing
hide timer::sensing
(My 100th Post!)
(days since 2000)
(timer)
- DerpTrollWizrd
-
Scratcher
11 posts
Days since:
The show and hide has a workaround though
Yeah, just use
when green flag clicked
show variable [timer v]
repeat until <(timer off) = [true ]>
change [timer v] by (0.01)
wait (0.01) secs
end
hide variable [timer v]
when green flag clicked
wait (50) secs
set [timer off v] to [true ]
- DaSpudLord
-
Scratcher
1000+ posts
Days since:
(days since ()::sensing)Why do we need this?
show timer::sensingNo support. Use a variable.
hide timer::sensing
- DerpTrollWizrd
-
Scratcher
11 posts
Days since:
I dunno. same reason we need(days since ()::sensing)Why do we need this?show timer::sensingNo support. Use a variable.
hide timer::sensing
(days since 2000)
- Abstract-
-
Scratcher
1000+ posts
Days since:
<Offtopic> You can actually caculate timezones with that block and some complex funtions. </Offtopic>I dunno. same reason we need(days since ()::sensing)Why do we need this?show timer::sensingNo support. Use a variable.
hide timer::sensing(days since 2000)
Support for all three.
- DaSpudLord
-
Scratcher
1000+ posts
Days since:
But why does it need to be changed with the input?I dunno. same reason we need(days since ()::sensing)Why do we need this?show timer::sensingNo support. Use a variable.
hide timer::sensing(days since 2000)
- DerpTrollWizrd
-
Scratcher
11 posts
Days since:
because… reasons.But why does it need to be changed with the input?I dunno. same reason we need(days since ()::sensing)Why do we need this?show timer::sensingNo support. Use a variable.
hide timer::sensing(days since 2000)
- DaSpudLord
-
Scratcher
1000+ posts
Days since:
Yeah, that's why I don't support.because… reasons.But why does it need to be changed with the input?I dunno. same reason we need(days since ()::sensing)Why do we need this?show timer::sensingNo support. Use a variable.
hide timer::sensing(days since 2000)
- redgreenandblue
-
Scratcher
100+ posts
Days since:
Oh, whoops. I forgot theAll of them would be in sensing.Yes, but they would be in different categories.This is a duplicate but I support! Also, you should look at this: https://scratch.mit.edu/discuss/topic/201279/?page=2#post-2018629 It has the rules to block suggesting. (it isn't a sticky but these are still real rules)Since these are only 3 blocks, I guess it's fine.(days since ()::operators)If they were in the same category then that would be fine.
show timer::sensing
hide timer::sensing
(My 100th Post!)(days since 2000)
(timer)
(days since 2000)was operators.
My bad

- DerpTrollWizrd
-
Scratcher
11 posts
Days since:
uuhhh… it's sensing actually…Oh, whoops. I forgot theAll of them would be in sensing.Yes, but they would be in different categories.This is a duplicate but I support! Also, you should look at this: https://scratch.mit.edu/discuss/topic/201279/?page=2#post-2018629 It has the rules to block suggesting. (it isn't a sticky but these are still real rules)Since these are only 3 blocks, I guess it's fine.(days since ()::operators)If they were in the same category then that would be fine.
show timer::sensing
hide timer::sensing
(My 100th Post!)(days since 2000)
(timer)(days since 2000)was operators.
My bad
- ProjectMaker59
-
Scratcher
500+ posts
Days since:
(days since () :: sensing) // duplicate but support
show timer :: sensing // there's a workaround, no support sorry
hide timer :: sensing // there's a workaround, no support sorry
// the workarounds is in my project
- Paddle2See
-
Scratch Team
1000+ posts
Days since:
It looks like this is a duplicate topic of this one over here so I'll close it to keep the conversation all in one place.
Please use the existing topic in the link above.
Please use the existing topic in the link above.
- Discussion Forums
- » Suggestions
-
» Days since:








