GabrielBoms wrote:

soarroying wrote:

(#14)

fireincarnate wrote:

I still like having the minimum amount of scripts in my sprites, even if it means having a giant script.

Same, but this suggestion has a legit workaround

when green flag clicked
whatever you want here :: custom
when [space v] key pressed
whatever you want here :: custom
define whatever you want here
A script :: #284

cool

when (when green flag clicked :: hat) [or v] (when [space v] key pressed :: hat) :: operators hat

when (when green flag clicked :: hat) [and v] (when [1 v] key pressed :: hat) :: operators hat

GabrielBoms wrote:

when (when green flag clicked :: hat) [and v] (when [1 v] key pressed :: hat) :: operators hat

(credit to soarroying)

when (when green flag clicked :: hat) [xor v] (when [1 v] key pressed :: hat) :: operators hat

soarroying wrote:

(#24)

GabrielBoms wrote:

when (when green flag clicked :: hat) [and v] (when [1 v] key pressed :: hat) :: operators hat

(credit to soarroying)

You could also do

when (when green flag clicked :: hat) [xor v] (when [1 v] key pressed :: hat) :: operators hat

when (when green flag clicked :: hat) [or v] (when [1 v] key pressed :: hat) :: operators hat

EG hat block :: hat
workaround

when I receive [egample v]
workaround

define workaround
EG block
another EG block to represent script :: events
if <EG boolean: (EG number/text input) = (example)?> then
EG block
end

GabrielBoms wrote:

soarroying wrote:

(#24)

GabrielBoms wrote:

when (when green flag clicked :: hat) [and v] (when [1 v] key pressed :: hat) :: operators hat

(credit to soarroying)

You could also do

when (when green flag clicked :: hat) [xor v] (when [1 v] key pressed :: hat) :: operators hat

correction for ‘'xor’': xor

when (when green flag clicked :: hat) [xor v] (when [1 v] key pressed :: hat) :: operators hat

soarroying wrote:

GabrielBoms wrote:

soarroying wrote:

(#24)

GabrielBoms wrote:

when (when green flag clicked :: hat) [and v] (when [1 v] key pressed :: hat) :: operators hat

(credit to soarroying)

You could also do

when (when green flag clicked :: hat) [xor v] (when [1 v] key pressed :: hat) :: operators hat

correction for ‘'xor’': xor

when (when green flag clicked :: hat) [xor v] (when [1 v] key pressed :: hat) :: operators hat

xor is true if one statment is true and the other one is false.

do this [when space key pressed v] or [when green flag clicked v]::events hat

Plasmoxxie wrote:

Why did everyone ignore this much simpler concept?

do this [when space key pressed v] or [when green flag clicked v]::events hat

It's simple enough for new users to tell what it does, and it doesn't use block stacking in any way whatsoever.
Does this not make sense?

when [green flag clicked v] or [space key pressed v] @delInput @addInput :: events hat
// Or:
when [green flag clicked v] or [space key pressed v] @delInput @addInput :: operators hat

soarroying wrote:

Plasmoxxie wrote:

Why did everyone ignore this much simpler concept?

do this [when space key pressed v] or [when green flag clicked v]::events hat

It's simple enough for new users to tell what it does, and it doesn't use block stacking in any way whatsoever.
Does this not make sense?

Fixed mockup:

do this [when space key pressed v] or [when green flag clicked v] :: operators hat

Plasmoxxie wrote:

soarroying wrote:

Plasmoxxie wrote:

Why did everyone ignore this much simpler concept?

do this [when space key pressed v] or [when green flag clicked v]::events hat

It's simple enough for new users to tell what it does, and it doesn't use block stacking in any way whatsoever.
Does this not make sense?

Fixed mockup:

do this [when space key pressed v] or [when green flag clicked v] :: operators hat

How is that fixed? You just made it green.

soarroying wrote:

It should be operators

when I start as a clone

Plasmoxxie wrote:

soarroying wrote:

It should be operators

That doesn't really make sense, as every hat block that would work for this is in the Events category.
Besides, the only hat block NOT in the events category is

when I start as a clone

when [shaken v] :: pen
when () :: pen
when button ( v) pressed :: pen hat
when ( v) key pressed :: pen
when ( v) pressed in order :: pen hat
when titled () :: pen hat

soarroying wrote:

Plasmoxxie wrote:

soarroying wrote:

It should be operators

That doesn't really make sense, as every hat block that would work for this is in the Events category.
Besides, the only hat block NOT in the events category is

when I start as a clone

You're forgetting the new extension hats introduced in 3.0

when [shaken v] :: pen
when () :: pen
when button ( v) pressed :: pen hat
when ( v) key pressed :: pen
when ( v) pressed in order :: pen hat
when titled () :: pen hat

And I forgot the rest of them, so yeah.

when I receive [ v]

or...
when backdrop switches to [ v]

when (when green flag clicked :: hat) [or v] (when [space v] key pressed :: hat) do :: operators hat

Plasmoxxie wrote:

Why did everyone ignore this much simpler concept?

do this [when space key pressed v] or [when green flag clicked v]::events hat

It's simple enough for new users to tell what it does, and it doesn't use block stacking in any way whatsoever.
Does this not make sense?

HighFlyer222 wrote:

No support. This would confuse most of new Scratchers, and in my opinion, block inputs (the one you suggested, putting a block inside another block) don't fit well with Scratch. Also there must also be something like this i this gets implemented: (I think)

(hat 1::events hat) and (hat 2::events hat)::extension hat

sussy_baka1234567890 wrote:

HighFlyer222 wrote:

No support. This would confuse most of new Scratchers, and in my opinion, block inputs (the one you suggested, putting a block inside another block) don't fit well with Scratch. Also there must also be something like this i this gets implemented: (I think)

(hat 1::events hat) and (hat 2::events hat)::extension hat

no it wont! It would be cleaner to use than the workaround

EX hat :: hat
Workaround
EX hat :: hat
Workaround
define Workaround
repeat () 
EX block
end

k0d3rrr wrote:

Plasmoxxie wrote:

Why did everyone ignore this much simpler concept?

do this [when space key pressed v] or [when green flag clicked v]::events hat

It's simple enough for new users to tell what it does, and it doesn't use block stacking in any way whatsoever.
Does this not make sense?

Good idea, but a better block might be:

when [green flag clicked v] or [space key pressed v] @delInput @addInput :: events hat
// Or:
when [green flag clicked v] or [space key pressed v] @delInput @addInput :: operators hat

when [green flag clicked v] or [space key pressed v] @delInput @addInput :: control hat