Replace "Looks" blocks

iamunknown2

Reasons:

If there's a “next costume block”, why isn't there a “previous costume” block?
Why doesn't it have the option to specify the amount of costumes to skip?
The above implies that this “next costume” block is quite inconsistent and unnecessary.

Although I am aware that there are many posts suggesting to add “previous” costume, I am instead suggesting a new thing - instead of the rather specific

next costume

,
I propose a new block which would replace “next costume”:

switch costume to costume #[ ]

What do you think?

Aboot4

iamunknown2 wrote:
Reasons:
If there's a “next costume block”, why isn't there a “previous costume” block?
Why doesn't it have the option to specify the amount of costumes to skip?
The above implies that this “next costume” block is quite inconsistent and unnecessary.
Although I am aware that there are many posts suggesting to add “previous” costume, I am instead suggesting a new thing - instead of the rather specific
next costume
,
I propose a new block which would replace “next costume”:
switch costume to costume #[ ]
What do you think?

Easily workaroundable. No support.

switch costume to ((costume #) - (1))

Last edited by Aboot4 (June 30, 2015 13:28:42)

iamunknown2

Aboot4 wrote:
Easily workaroundable. No support.
switch costume to ((costume #) - (1))

What if costume # != costume name?

(!= means not equal to)

And I don't get why out of all potential relative costume-switching blocks, “next costume” is chosen.

Last edited by iamunknown2 (June 30, 2015 13:47:32)

thelucariokid

Support for

Switch costume to []::looks

Because I don't like having to look at the costume name every time I want to add the old block.

ElectroElectro2004

Aboot4 wrote:
Easily workaroundable. No support.
switch costume to ((costume #) - (1))

Couldn't agree more.

No support.

pokejofe

no support

TheHockeyist

switch costume to [ v]

can already do number input - just set a variable equal to a number and move the variable into the dropdown to plug it in.

Znapi

iamunknown2 wrote:
Aboot4 wrote:
Easily workaroundable. No support.
switch costume to ((costume #) - (1))
What if costume # != costume name?

There isn't a problem when costume # != costume name. There is a problem when costume # does == costume name.

If you put a number into the switch costume block, first it will look for a costume named that number. If it can't find one, then it switches to the costume at that number.

Last edited by Znapi (June 30, 2015 16:38:08)

Pot-of-Gold

No support:
Workaround:

switch costume to (join [] [number of costume])

Aboot4

iamunknown2 wrote:
Aboot4 wrote:
Easily workaroundable. No support.
switch costume to ((costume #) - (1))
What if costume # != costume name?

(!= means not equal to)

And I don't get why out of all potential relative costume-switching blocks, “next costume” is chosen.

Because its not talking about costume names. It's talking about the costume order in the list of costumes in the “costume” tab.

iamunknown2

Aboot4 wrote:

switch costume to ((costume #) - (1))

Did you even read the post? I'm not suggesting previous costume blocks.

And what if costume name != costume number?

iamunknown2

TheHockeyist wrote:
switch costume to [ v]
can already do number input - just set a variable equal to a number and move the variable into the dropdown to plug it in.

What if you want to keep their names? Then you would have to do

repeat until <(costume #) = (desired costume)>
next costume
end

Pot-of-Gold

iamunknown2 wrote:
TheHockeyist wrote:
switch costume to [ v]
can already do number input - just set a variable equal to a number and move the variable into the dropdown to plug it in.
What if you want to keep their names? Then you would have to do
repeat until <(costume #) = (desired costume)>
next costume
end

USe this workaround:

Pot-of-Gold wrote:
No support:
Workaround:
switch costume to (join [] [number of costume])

iamunknown2

Pot-of-Gold wrote:
iamunknown2 wrote:
TheHockeyist wrote:
switch costume to [ v]
can already do number input - just set a variable equal to a number and move the variable into the dropdown to plug it in.
What if you want to keep their names? Then you would have to do
repeat until <(costume #) = (desired costume)>
next costume
end
USe this workaround:
Pot-of-Gold wrote:
No support:
Workaround:
switch costume to (join [] [number of costume])

Did you even read the post?

What if you want to keep their names?

Pot-of-Gold

iamunknown2 wrote:
Pot-of-Gold wrote:
iamunknown2 wrote:
TheHockeyist wrote:
switch costume to [ v]
can already do number input - just set a variable equal to a number and move the variable into the dropdown to plug it in.
What if you want to keep their names? Then you would have to do
repeat until <(costume #) = (desired costume)>
next costume
end
USe this workaround:
Pot-of-Gold wrote:
No support:
Workaround:
switch costume to (join [] [costume name])
Did you even read the post?
What if you want to keep their names?

FIxed it to show there is another workaround. And yes i did

iamunknown2

Pot-of-Gold wrote:
iamunknown2 wrote:
Pot-of-Gold wrote:
iamunknown2 wrote:
TheHockeyist wrote:
switch costume to [ v]
can already do number input - just set a variable equal to a number and move the variable into the dropdown to plug it in.
What if you want to keep their names? Then you would have to do
repeat until <(costume #) = (desired costume)>
next costume
end
USe this workaround:
Pot-of-Gold wrote:
No support:
Workaround:
switch costume to (join [] [costume name])
Did you even read the post?
What if you want to keep their names?
FIxed it to show there is another workaround. And yes i did

You didn't change anything…

TylerInScratch

Aboot4 wrote:
iamunknown2 wrote:
Reasons:
If there's a “next costume block”, why isn't there a “previous costume” block?
Why doesn't it have the option to specify the amount of costumes to skip?
The above implies that this “next costume” block is quite inconsistent and unnecessary.
Although I am aware that there are many posts suggesting to add “previous” costume, I am instead suggesting a new thing - instead of the rather specific
next costume
,
I propose a new block which would replace “next costume”:
switch costume to costume #[ ]
What do you think?
Easily workaroundable. No support.
switch costume to ((costume #) - (1))

I agree!

when flag is still standing

be happy!

TylerInScratch

TylerInScratch wrote:
Aboot4 wrote:
iamunknown2 wrote:
Reasons:
If there's a “next costume block”, why isn't there a “previous costume” block?
Why doesn't it have the option to specify the amount of costumes to skip?
The above implies that this “next costume” block is quite inconsistent and unnecessary.
Although I am aware that there are many posts suggesting to add “previous” costume, I am instead suggesting a new thing - instead of the rather specific
next costume
,
I propose a new block which would replace “next costume”:
switch costume to costume #[ ]
What do you think?
Easily workaroundable. No support.
switch costume to ((costume #) - (1))
That flag thing was kinda unporposeful

Pot-of-GoId

iamunknown2 wrote:
Pot-of-Gold wrote:
iamunknown2 wrote:
Pot-of-Gold wrote:
iamunknown2 wrote:
TheHockeyist wrote:
switch costume to [ v]
can already do number input - just set a variable equal to a number and move the variable into the dropdown to plug it in.
What if you want to keep their names? Then you would have to do
repeat until <(costume #) = (desired costume)>
next costume
end
USe this workaround:
Pot-of-Gold wrote:
No support:
Workaround:
switch costume to (join [] [costume name])
Did you even read the post?
What if you want to keep their names?
FIxed it to show there is another workaround. And yes i did
You didn't change anything…

switch to costume name

iamunknown2

Pot-of-GoId wrote:
iamunknown2 wrote:
Pot-of-Gold wrote:
FIxed it to show there is another workaround. And yes i did
You didn't change anything…
switch to costume name

Then it wouldn't be a workaround for

switch costume to costume # [ ]

any more…

Last edited by iamunknown2 (July 1, 2015 07:51:35)

Discuss Scratch