Discuss Scratch

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

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:

redgreenandblue wrote:

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:

Lythium wrote:

redgreenandblue wrote:

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.
Yes, but they would be in different categories.
(days since ()::operators)
show timer::sensing
hide timer::sensing
If they were in the same category then that would be fine.
(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:

redgreenandblue wrote:

Lythium wrote:

redgreenandblue wrote:

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.
Yes, but they would be in different categories.
(days since ()::operators)
show timer::sensing
hide timer::sensing
If they were in the same category then that would be fine.
(My 100th Post!)
All of them would be in sensing.

(days since 2000)
(timer)
DerpTrollWizrd
Scratcher
11 posts

Days since:

rasmusolle wrote:

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::sensing

hide timer::sensing
No support. Use a variable.
DerpTrollWizrd
Scratcher
11 posts

Days since:

DaSpudLord wrote:

(days since ()::sensing)
Why do we need this?
show timer::sensing

hide timer::sensing
No support. Use a variable.
I dunno. same reason we need
(days since 2000)
Abstract-
Scratcher
1000+ posts

Days since:

DerpTrollWizrd wrote:

DaSpudLord wrote:

(days since ()::sensing)
Why do we need this?
show timer::sensing

hide timer::sensing
No support. Use a variable.
I dunno. same reason we need
(days since 2000)
<Offtopic> You can actually caculate timezones with that block and some complex funtions. </Offtopic>

Support for all three.
_Comicfan_
Scratcher
1000+ posts

Days since:

Support.
DaSpudLord
Scratcher
1000+ posts

Days since:

DerpTrollWizrd wrote:

DaSpudLord wrote:

(days since ()::sensing)
Why do we need this?
show timer::sensing

hide timer::sensing
No support. Use a variable.
I dunno. same reason we need
(days since 2000)
But why does it need to be changed with the input?
DerpTrollWizrd
Scratcher
11 posts

Days since:

DaSpudLord wrote:

DerpTrollWizrd wrote:

DaSpudLord wrote:

(days since ()::sensing)
Why do we need this?
show timer::sensing

hide timer::sensing
No support. Use a variable.
I dunno. same reason we need
(days since 2000)
But why does it need to be changed with the input?
because… reasons.
DaSpudLord
Scratcher
1000+ posts

Days since:

DerpTrollWizrd wrote:

DaSpudLord wrote:

DerpTrollWizrd wrote:

DaSpudLord wrote:

(days since ()::sensing)
Why do we need this?
show timer::sensing

hide timer::sensing
No support. Use a variable.
I dunno. same reason we need
(days since 2000)
But why does it need to be changed with the input?
because… reasons.
Yeah, that's why I don't support.
redgreenandblue
Scratcher
100+ posts

Days since:

Lythium wrote:

redgreenandblue wrote:

Lythium wrote:

redgreenandblue wrote:

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.
Yes, but they would be in different categories.
(days since ()::operators)
show timer::sensing
hide timer::sensing
If they were in the same category then that would be fine.
(My 100th Post!)
All of them would be in sensing.

(days since 2000)
(timer)
Oh, whoops. I forgot the
(days since 2000)
was operators.
My bad
DerpTrollWizrd
Scratcher
11 posts

Days since:

redgreenandblue wrote:

Lythium wrote:

redgreenandblue wrote:

Lythium wrote:

redgreenandblue wrote:

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.
Yes, but they would be in different categories.
(days since ()::operators)
show timer::sensing
hide timer::sensing
If they were in the same category then that would be fine.
(My 100th Post!)
All of them would be in sensing.

(days since 2000)
(timer)
Oh, whoops. I forgot the
(days since 2000)
was operators.
My bad
uuhhh… it's sensing actually…
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
Lythium
Scratcher
1000+ posts

Days since:

Support for all 3.
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.

Powered by DjangoBB