Scratch

cool

DrSuper wrote:

In a forever loop set x and y of the selected sprite to the x and y of the mouse
Inside this loop it keep the equality as long and the mouse is pressed (the sprite is getting dragged) as soon as the mouse is released stop the script.

Yeah, that's the basic way to do it. But you'll notice that the sprite "jumps" to the mouse pointer rather than being offset and moving relatively with the mouse. Try comparing the two sometime!

DrSuper wrote:

One question for you. Do you know how we can get the shadow that sprites have in design at run time when they are selected?

The shadow you get when dragging them? No, I don't think that's possible. You could make  a copy of the sprite, crank its brightness down to -100, and add code like this:

On the original sprite (we'll call it Cat):

When flag clicked:
Forever:
If <<touching mouse pointer?> and <mouse down?>>
set myDragged to 1 (this is a variable for "this sprite only"
Else:
set myDragged to 0

On the shadow:

When flag clicked:
Forever:
If <(myDragged of Cat)=1>
Show
Go to x: (x pos of Cat)-10 y: (y pos of Cat)-10
Else
Hide

The shadow is Scratch's way of reminding you that just because a sprite is draggable in edit mode doesn't mean it'll work in presentation or online.

Thanks for sharing your tips. They are really precious, I'm sure.

JSO wrote:

fullmoon wrote:

Say <Boolean> for 2 seconds

It's possible to put a boolean (triangle-cornered) block into "say" or "think" blocks. The sprite will say either "true" or "false".

Boolean block?
Where can I find it?

I tried with a variable 0 or 1...

Joren

I think fullmoon is refering to a block that returns a boolean value, such as "Touching Color", "Key Pressed",  and so on.

Cyclone103 wrote:

Paddle2See wrote:

JSO wrote:

Boolean block?
Where can I find it?

I tried with a variable 0 or 1...

Joren

I think fullmoon is refering to a block that returns a boolean value, such as "Touching Color", "Key Pressed",  and so on.

Mouse down is another block that returns a boolean value. Although, I see no reason for a sprite to say if the mouse button is clicked.....

Yeah, it's not really that useful...actually, it was probably an accident.

Thanks fullmoon. I will try out your suggestion on shadow and mouse movement. With unlocking I could not get what I needed to be able to drop the sprite exactly on another sprite if it is touching it. Probably inexperience for now. I have been feverishly completing my game to post it this week;=>

Bluestribute wrote:

And dragging local variables into other sprites makes a new local variable (if it's not up there)

That one I knew. I tried that for myself! If you drag "if sprite one clicked" from control onto another sprite, it adapts.

I have tried unlocking sprites and moving them I have the following issues:
1. I need a way to dynamically lock or unlock a sprite.
2. A locked sprite considers mouse down as a click but for an unlocked sprite "clicked" means the mouse has been pressed and has come up in a short (?) time interval. If I just drag an unlocked sprite it is not considered "clicked" and the scripts will not start firing until you actually click the sprite. Do you know a way around this. I really need a mouse down event for unlocked sprites;=<
Regards
Dr. Super

Fullmoon et all
I just posted my first game try to beat Dr. Super;>  and pass on the word if you like it.
http://scratch.mit.edu/projects/DrSuper/206349

PetertheGeek wrote:

Good tips! I really like the boolean one. I knew you could do it, but I thought it would just bring up an error.

Also, I don't know whether you want to include these, but here they are.

1) You can right click the script area and click "Clean Up" and it will put all of the scripts in one nice neat column.

2) You can right click the script area and click "Save Picture of Scripts" and then select a destination for the image to save to.

3) You can right click the stage and click "Grab Screen Region for New Sprite" and then select any region in the Scratch program and it will turn it into a new sprite.

4) You can right click the stage and click "Save Picture of Stage" and select a destination for the image to save to.

5) You can hold the shift key while encreasing or decreasing a sprite's size to make it increase/decrease in large increments.

Cool! I didn't know about the shift key one.

I dont know if this tip has already been mentioned somewhere on the forums but i'll mention it anyway.
If you have a project with lots of forever loops that is running slowly on or off the internet you can make it run better by coppying everything in the loop two or three times and adding a small wait of maybe 0.01 seconds.  this should help it run on slower computers.
for example instead of:
forever,
move 1 step

you could do:
forever,
move 1 step
move 1 step
move 1 step
wait 0.01 seconds.

Use variables for numbers you use more than 2-3 times.
Then, if you're testing or want to change something, you only need to change the variable and not all 50 instances of the number!