RPFluffy wrote:

Langdon35 wrote:

RPFluffy wrote:

MegaApuTurkUltra wrote:

Try some hacks

define keyPressesInList_allRequired
set [i v] to (1)
repeat (length of [presses v])
if <not<key (item (i) of [presses v]) pressed?>>
set [yes v] to (0) // idk if key pressed accepts a reporter. Try it! Otherwise edit the json
stop [this script v] // if not ALL keys in the list are pressed, return 0
end
change [i v] by (1)
end
set [yes v] to (1) // all keys in list pressed, return 1

define keyPressesInList_oneRequired
set [i v] to (1)
repeat (length of [presses v])
if <key (item (i) of [presses v]) pressed?>
set [yes v] to (1)
stop [this script v] // if at least ONE of the keys is pressed, return 1
end
change [i v] by (1)
end
set [yes v] to (0) // no keys in the list are pressed, return 0

The stop […] blocks are in there to prevent unnecessary looping, which will slow your project down. Make sure to use custom blocks like above because then stop this script will only stop the custom block. Also make sure to make the custom blocks run without screen refresh to speed up the looping.

Try this ^
It works…

Yes it does, also, I think it would be a better idea to use this than make a new block :3

Um, that's basically what I said don't do that, its called spam FYI

when green flag clicked
forever
if <not <key [any v] pressed?>> then
delete (1 v) of [list v]
end
if <key [space v] pressed?> then
replace item (1 v) of [list v] with [space]
end

end

when green flag clicked
forever
if <key [ (item (Any))  of Key List pressed?> then
                 -your script goes here
end
end

<key [c v] pressed?>

Nambaseking01 wrote:

I don't understand. Doesn't this block already exist?

<key [c v] pressed?>

I have a feeling I am missing something. Could someone please explain?

(which keys pressed? :: sensing)

Sensing :: sensing hat

(Key Pressed :: sensing reporter)

define find key pressed
forever
    if <key [any v] pressed?> then
        set [keys v] to (keys you want to detect::undefined)
        set [incroment v] to [1]
        repeat (length of (keys)::operators)
            if <key (letter (incroment) of (keys)) pressed?> then
                set [key pressed v] to (letter (incroment) of (keys))
            end
            change [incroment v] by (1)
        end
        if <key (join [enter] []) pressed?> then
            set [key pressed v] to [enter]
        end
        if <key [space v] pressed?> then
            set [key pressed v] to [space]
        end
        say (key pressed)
    else
        say [no key is pressed]
    end
end

sathvikrias wrote:

here is a workaround, which doesn't involve doing letter-for-letter:

define find key pressed
forever
    if <key [any v] pressed?> then
        set [keys v] to (keys you want to detect::undefined)
        set [incroment v] to [1]
        repeat (length of (keys)::operators)
            if <key (letter (incroment) of (keys)) pressed?> then
                set [key pressed v] to (letter (incroment) of (keys))
            end
            change [incroment v] by (1)
        end
        if <key (join [enter] []) pressed?> then
            set [key pressed v] to [enter]
        end
        if <key [space v] pressed?> then
            set [key pressed v] to [space]
        end
        say (key pressed)
    else
        say [no key is pressed]
    end
end

if <[enemy list] contains <touching [sprite] ?> ?> then
broadcast [hurt]
end

<<<touching [enemy1] ?>> or <<<touching [enemy2] ?>> or <<<touching [enemy3] ?>> or <<<touching [enemy4] ?>> or <<<touching [enemy5] ?>> or <touching [enemy6] ?>>>>>>

Futurebot5 wrote:

That workaround is to long for how useful the suggestion is.

Mad__Moss wrote:

Hi,

I had an idea, what about a Sensor Reporter block that contained the key that was currently being pressed? If this existed, then you could have a list with all the keys that perform a specific function in it and make:

if <[Task 1 Keys v] contains [(key pressed)]> then
    ...
end

Instead of having:

if <<<<<key [... v] pressed?> or <key [... v] pressed?>> or <key [... v] pressed?>> or <key [... v] pressed?>> or <key [... v] pressed?>> then
    ...
end

And needing to repeat and change that every time you changed your mind.

Anybody else think that this is a good idea?

From Mad__Moss

moonwatcher348 wrote:

@sathvikrias that doesn't work, I see no reason it shouldn't though

<keys [space v] @delInput @addInput are pressed? :: sensing>//2.0
<keys (space v) @delInput @addInput are pressed? :: sensing>//3.0

mcgoomba wrote:

<keys [space v] @delInput @addInput are pressed? :: sensing>//2.0
<keys (space v) @delInput @addInput are pressed? :: sensing>//3.0

is that what the block's gonna looks like?

(key pressed :: sensing) //returns the last pressed key

abcdqwery

Mad__Moss wrote:

Langdon35 wrote:

RPFluffy wrote:

Langdon35 wrote:

RPFluffy wrote:

MegaApuTurkUltra wrote:

Try some hacks

define keyPressesInList_allRequired
set [i v] to (1)
repeat (length of [presses v])
if <not<key (item (i) of [presses v]) pressed?>>
set [yes v] to (0) // idk if key pressed accepts a reporter. Try it! Otherwise edit the json
stop [this script v] // if not ALL keys in the list are pressed, return 0
end
change [i v] by (1)
end
set [yes v] to (1) // all keys in list pressed, return 1

define keyPressesInList_oneRequired
set [i v] to (1)
repeat (length of [presses v])
if <key (item (i) of [presses v]) pressed?>
set [yes v] to (1)
stop [this script v] // if at least ONE of the keys is pressed, return 1
end
change [i v] by (1)
end
set [yes v] to (0) // no keys in the list are pressed, return 0

The stop […] blocks are in there to prevent unnecessary looping, which will slow your project down. Make sure to use custom blocks like above because then stop this script will only stop the custom block. Also make sure to make the custom blocks run without screen refresh to speed up the looping.

Try this ^
It works…

Yes it does, also, I think it would be a better idea to use this than make a new block :3

Um, that's basically what I said don't do that, its called spam FYI

Ok, thanks for the info.

Mad__Moss wrote:

Really? Anyone have more ideas on how the block would work?

maybe this:

if <keys pressed> then //there would be a check box list of keys that could be pressed.
    ...
end

Or you could have a list with the keys you want to be pressed:

if <(item (all v) of [Key List v]) = [(key pressed)]> then //If ALL of the items in Key List are pressed then:
    ...
end

That way you could change the keys that need to be pressed more easily.