Scratch

A way around the pause before repeat is to do
If <key (whatever key) pressed>
do action
========

and a way around the mouse click is to do
if < <mouse down> and <touching mouse-pointer> >
do action
wait until <not <mouse down> >

Or you could do (for the mouse), use the when (sprite) clicked hat, but there is a delay and you can't put it into wait untils or anything.

Hope this helped!

Last edited by coolstuff (2008-07-31 11:07:04)

SonicPopsDad wrote:

Coolstuff,

I'm not sure I get the key example (which is a bit embarrassing as it looks so simple!), because it looks the same as the movement routine I wrote this morning (for an Asteroids game), which looked like this (iirc)...

Spaceship sprite
forever
   if key Left Arrow pressed
        rotate ...

   if key Right Arrow pressed
        rotate ...
(repeat)

However I definitely *do* get the mouse one, that's great and should cure my problem!  thankyou!

Hm... the repeat-after-wait thinghymabobber only happens really when I use the when ___ key pressed hat (script header). I don't know what could've happened there.

You know, I should really answer these forum posts when I'm at home, and I can try to replicate my original problems ...      I can't remember what I did that made the key board input work poorly, but Paddle2See, the project you posted works perfectly (though it's what I htought I'd originally done!) ...  I copied the code into my Defender game, and it's great     (I''ve now got mouse *and* keyboard input working for it, which will suit old-school gamers like me!)

edit: oh yeah, Coolstuff mentioned it - must've used the 'when key pressed' block rather than the sensor module

Last edited by SonicPopsDad (2008-08-01 09:27:45)

I think this is the "problem":

[blocks]
<when[  ]key pressed>
[/blocks]
This is an event: it depends on the key repeat in windows. Try holding a kay in wordpad and see what happens...



[blocks]
<key[  ]pressed?>
<mouse down?>
[/blocks]

These variables are actually some kind of boolean variables: true/false. When you put in a loop it might loop  or more times trough it because the condition keeps true. Adding a 0.1 wait might solve the problem.

cheers guys, I've got a new project http://scratch.mit.edu/projects/SonicPopsDad/231508 which makes use of the mouse wait.  I've got another project on the go which actually uses the single-key input effect as a positive thing, so it's good we've got access to alternatives!

newareagle: thanks for pointing out 'broadcast and wait' ... I hadn't noticed that, I've used 'waits' and timers to get around any issues I've had - that way will be nicer