Scratch
archived forums
#1 2012-04-14 14:50:04
Yet Another 'New Block' Idea... The <I recieve _____> Block!
(In the Sensing section, a hexagon block (Mainly for Wait Until's)
Basic Idea:
<I receive [SOMETHING]>In Context:
Sprite 1-
when gf clicked
forever
if <(variable) = (10)>
broadcast [go]
end
end
Sprite 2-when gf clicked scream say [LOUDNESS!] for (18) secs wait until <I receive [go]> set [ghost] effect to [15] switch to costume [costume5] point in direction [90] move [10] stepsOr, of course, (*sigh*), there is the workaround...
Sprite 1-
when gf clicked
set (variable2) to [0]
forever
if <(variable) = (10)>
set (variable2) to [1]
end
end
Sprite 2-when gf clicked scream say [LOUDNESS!] for (18) secs wait until <(variable2) = [1]> set [ghost] effect to [15] switch to costume [costume5] point in direction [90] move [10] stepsBut, anyway, just an idea!
Isn't he CUTE?!Offline
#2 2012-04-14 16:51:08
- northmeister
- Scratcher
- Registered: 2011-07-12
- Posts: 1000+
Re: Yet Another 'New Block' Idea... The <I recieve _____> Block!
I think this would be a great new block, it could be really useful 
Offline
#5 2013-04-26 13:05:09
- joefarebrother
- Scratcher
- Registered: 2011-04-08
- Posts: 1000+
Re: Yet Another 'New Block' Idea... The <I recieve _____> Block!
It would only be true for one millisecond when put in an if or a repeat until block, so it will only really be useful in a wait until block. So either we have
wait until i receive [... v]or
<i received [... v] in the last (2) seconds>Also it would be in the control catagory not the sensing catagory.
Last edited by joefarebrother (2013-04-26 13:05:38)
My latest project is called
Offline
#6 2013-04-26 16:51:11
Re: Yet Another 'New Block' Idea... The <I recieve _____> Block!
joefarebrother wrote:
Also it would be in the control catagory not the sensing catagory.
([x position v] of [sprite1 v])is in sensing.
Tip of the whatever: Don't post in threads older than 2 weeks unless your post will actually be useful.
It's the last day of 1.4! *cries* (quote from NeilWest, rest by me) by the time you read this it probably will be 2.0
Offline
#7 2013-04-27 04:58:30
- joefarebrother
- Scratcher
- Registered: 2011-04-08
- Posts: 1000+
Re: Yet Another 'New Block' Idea... The <I recieve _____> Block!
Hyperbola wrote:
joefarebrother wrote:
Also it would be in the control category not the sensing catagory.
([x position v] of [sprite1 v])is in sensing.
I know, but broadcasts are part of the control category so it doesn't make sense to have a broadcast-related block in a different category.
My latest project is called
Offline
#8 2013-04-27 20:40:04
- Scratch12300
- New Scratcher
- Registered: 2013-04-13
- Posts: 38
Re: Yet Another 'New Block' Idea... The <I recieve _____> Block!
<I recieve [message1 v]>is a good idea!
Offline
#9 2013-04-27 23:23:57
Re: Yet Another 'New Block' Idea... The <I recieve _____> Block!
Do you really think there's no reason why the ST hasn't ever added this?!? The boolean needs to report true/false, right? But that's only when the script is checking for it. Try single stepping and think about it. This block isn't realistic. It's a good, but unlikely idea, as this block would almost NEVER report true. I'd support if it was realistic.
Offline
#10 2013-04-28 03:21:32
- shadowmouse
- New Scratcher
- Registered: 2013-02-03
- Posts: 100+
Re: Yet Another 'New Block' Idea... The <I recieve _____> Block!
It's actually quite easy to put in (at least for scratch 1.4, it's in the block library) and works perfectly in wait untils and repeat untils.
Offline
#11 2013-04-28 20:13:44
- Scratch12300
- New Scratcher
- Registered: 2013-04-13
- Posts: 38
Re: Yet Another 'New Block' Idea... The <I recieve _____> Block!
joefarebrother wrote:
It would only be true for one millisecond when put in an if or a repeat until block, so it will only really be useful in a wait until block. So either we have
wait until i receive [... v]or<i received [... v] in the last (2) seconds>Also it would be in the control catagory not the sensing catagory.
Or,
<I ever recieved [message1 v]>
Offline