Scratch

Greenatic wrote:

WingsGames wrote:

I have a suggestion: a "set answer to" block.

That should be pretty simple.  However, the purpose of the (answer) value is to represent user input, not a variable value.

Yes, but without it, if the user entered their password using the the < password for () is () > block, it would be stored in the answer variable until they typed in something else.

zippynk wrote:

Greenatic wrote:

WingsGames wrote:

I have a suggestion: a "set answer to" block.

That should be pretty simple.  However, the purpose of the (answer) value is to represent user input, not a variable value.

Yes, but without it, if the user entered their password using the the < password for () is () > block, it would be stored in the answer variable until they typed in something else.

Yep. That is a good idea. 

I have a suggestion for a block in the sensing category:

<Coordinates x: ( ) y: ( ) touching color [  ]>

it would be able to fit into the < > fields and would be useful for platformer sensing in combination with the (min x), (min y), (max x), and (max y) blocks.

Thanks!

you can do that so easily in panther. Just do
<(!colour of pixel at x:() y:()! as string) = (!colour you are testing for! as string)>

joefarebrother wrote:

you can do that so easily in panther. Just do
<(!colour of pixel at x:() y:()! as string) = (!colour you are testing for! as string)>

I was thinking the same thing, only touching would mean having any of the pixels AROUND it as well. 

Nireckda815 wrote:

I have a suggestion for a block in the sensing category:

<Coordinates x: ( ) y: ( ) touching color [  ]>

it would be able to fit into the < > fields and would be useful for platformer sensing in combination with the (min x), (min y), (max x), and (max y) blocks.

Thanks!

OK, here's the code:

  (Requested)

(coordinates x:%n y:%n touching color %c?' #b #X:y:touching:)

X: t1 y: t2 touching: t3
                |t4 |
    t4 _ #() asOrderedCollection.
    t1 isInf | t1 isNaN | t2 isInf | t2 isNaN ifTrue: [^ false].
    #((1 -1) (1 0) (1 1) (0 1) (-1 1) (-1 0) (-1 -1) (0 -1) ) do: [:t5 | t4 add: ScratchOrigin + ((t5 at: 1)
                    @ (t5 at: 2)) + (t1 rounded @ t2 rounded)].
    t4 do: 
        [:t6 | 
        t6 x > (ScratchOrigin x + 240) ifTrue: [t6 _ ScratchOrigin x + 240 @ t6 y].
        t6 x < (ScratchOrigin x - 240) ifTrue: [t6 _ ScratchOrigin x - 240 @ t6 y].
        t6 y > (ScratchOrigin y + 180) ifTrue: [t6 _ t6 x @ (ScratchOrigin y + 180)].
        t6 y < (ScratchOrigin y - 180) ifTrue: [t6 _ t6 x @ (ScratchOrigin y - 180)]].
    t4 do: 
        [:t7 | 
        (Display colorAt: t7)
            = t3 ifTrue: [^ true].
        nil].
    ^ false

Last edited by Greenatic (2011-12-17 10:45:41)

scimonster wrote:

When are we getting an update done around here?
I'm way too busy to do one. 

Yeah, I don't think an update has been done since page 72.   

I'm going to try to free up some time.  No guarantees, though.

Panther block: update from [] with version []
This block performs an automatic update from the URL specified. The URL should point to a directory containing (at least) a file named version.txt, and a file named <first line of version.txt>.pt (the most recent version of the project). The second argument to the block specifies the current version of the project. If the user is using an outdated project (the version is not the same as the first line of version.txt), he/she is asked if he/she wants to download the new version. If so, the new version is downloaded, opened, and run.

(-) update from $String$ with version $String$

"Usage: provide a directory URL with version.txt and (first line of version.txt).pt"
| version frame dir name stream |

(t1 endsWith: '/') ifFalse: [t1 := t1, '/'].
frame := ScratchFrameMorph allInstances first.
version := (HTTPSocket httpGet: t1, 'version.txt') contents lines first.
version = t2 ifTrue: [^ self].

(DialogBoxMorph ask: 'A new version (', version, ') is available. Would you like to download it?') ifFalse: [^ self].

name := frame projectName, '.pt'.

(dir := frame projectDirectory) deleteFileNamed: name.

stream := (dir newFileNamed: version, '.pt').
stream reset.
stream nextPutAll: (HTTPSocket httpGet: t1, version, '.pt') contents.

frame openScratchProjectNamed: dir pathName, dir slash, version, '.pt'; shoutGo.

Last edited by nXIII (2011-12-15 18:06:09)

Has .BLOCK development frozen?   

Last edited by Greenatic (2011-12-17 13:17:02)

Pecola1 wrote:

Greenatic wrote:

Has .BLOCK development frozen?   

Uh... I think so. XD

Darn.

*cue the trumpets* Update underway! Now let's hope I don't completely mess this up...      And don't expect me to get through 16 pages of library today.  That's not going to happen.

Last edited by Greenatic (2011-12-17 14:31:51)

Here is a sound amplitude recorder and writer.(Sorry, it cannot replay the music)
<when green flag clicked>< delete (all) of [amp]><go to x   -240 )y 0) <pen up><clear><set pen color to( 0)<point in direction( 0)<pen down><recorddb>

recorddb is:
<<forever><<repeat( 480)<set y to( <loudness>)<change x by(1)<add <loudness> to [amp]><end>>
<clear><pen up><go to x -240 )y   0)><pen down><end>>

ianidani wrote:

Here is a sound amplitude recorder and writer.(Sorry, it cannot replay the music)
[blocks]<when green flag clicked>< delete (all) of [amp]><go to x   -240 )y 0) <pen up><clear><set pen color to( 0)<point in direction( 0)<pen down><recorddb>

recorddb is:
<<forever><<repeat( 480)<set y to( <loudness>)<change x by(1)<add <loudness> to [amp]><end>>
<clear><pen up><go to x -240 )y   0)><pen down><end>>[/blocks]

use new lines between blocks like this:

[blocks]<when green flag clicked>
< delete (all) of [amp]>
<go to x   -240 )y 0)
<pen up>
<clear><set pen color to( 0)
<point in direction( 0)
<pen down>
<recorddb>

recorddb is:
<<forever>
<<repeat( 480)
<set y to( <loudness>)
<change x by(1)
<add <loudness> to [amp]>
<end>> [/blocks]




Oh, and please remember the

[blocks][/blocks]

tage when you use the blocks.

Last edited by joefarebrother (2011-12-17 16:41:24)

YourLocalBlockLib wrote:

As of this update, Greenatic is now Top Scratch Blocks Contributor.

*applause*