Previous costume

Malthetalthee

Im not sure if this already is here, but I would love a block called previous costume.

Last edited by Malthetalthee (March 3, 2013 06:51:04)

SFollis

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

Last edited by SFollis (March 3, 2013 16:54:33)

Happy_echiniscus

if there is a next costume block there should be a previouse costume block. mabey a dop-down menu with next and previous…

Rumanti

Hmm…I agree

botcrusher

I agree

theamazingblob

Also, they should have a next/previous backdrop block. I know they have that in the dropdown for the switch backdrop to ______ block, but seems a little inconsistent with the costume blocks.

lunaluvgood

theamazingblob wrote:
Also, they should have a next/previous backdrop block. I know they have that in the dropdown for the switch backdrop to ______ block, but seems a little inconsistent with the costume blocks.

So why don't they make a block that says "Switch to ?

Ranchero

This could be a good idea.If you are making a project with number sprites for data and you might need a health pack.

switch costume to [Previous costume v]

NoxSpooth

Just do this:

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

Catgirl555

I know it is possible to switch to the previous costume like this………….

switch costume to [Costume# -1]

But this would be WAY simpler for new scratchers and inexperienced scratchers.

Previous costume

Reasons for this block:
1. Simplicity.
2. A quick easy way for new scratchers to switch to the previous costume.
3. It will prolly be easy for the Scratch team to create.

Supporters:
Catgirl555
ScratchinJoJo

Last edited by Catgirl555 (April 26, 2015 15:34:55)

NoxSpooth

The workaround is already pretty simple. Also:

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


previous costume

Therefore, I do not support.

zacadoole1

I think we need this block because I don't think new Scratchers (and when I say new Scratchers I mean true beginners, not just people with the rank new Scratcher) are going to be able to easily figure out NoxSpooth's solution, being new Scratchers and all and not being completely familiar with all the blocks and their functions (especially custom blocks). That being said, I half-support, because I don't think we need an entirely new block for it, maybe just a change to the current “next costume” block to add a dropdown for next or previous costume?

[next v] costume ::looks
[previous v] costume ::looks

Last edited by zacadoole1 (April 22, 2015 23:08:30)

Birdlegs

Looks good on paper, but Scratch is a learning environment. New users should have that push into understanding the use of math and such in programming. Previous costume would just hold their hands through it.

ScratchinJoJo

I support.
For all those people that are saying you can do it with the costume # - 1 workaround, ok you're right, but why did the Scratch team decide to make a ‘next costume’ block? Probably to make it easier. I think it is easier to understand with a next and previous block.

NoxSpooth

ScratchinJoJo wrote:
I support.
For all those people that are saying you can do it with the costume # - 1 workaround, ok you're right, but why did the Scratch team decide to make a ‘next costume’ block? Probably to make it easier. I think it is easier to understand with a next and previous block.

Making it too easier, however, is a problem, because if we made a block for every easy workaround, we will end up adding a bunch of unnecessary blocks, clogging up the library. There needs to be a balance, and I believe Scratch currently has it.

Last edited by NoxSpooth (April 26, 2015 11:49:03)

zacadoole1

NoxSpooth wrote:
ScratchinJoJo wrote:
I support.
For all those people that are saying you can do it with the costume # - 1 workaround, ok you're right, but why did the Scratch team decide to make a ‘next costume’ block? Probably to make it easier. I think it is easier to understand with a next and previous block.
Making it too easier, however, is a problem, because if we made a block for every easy workaround, we will end up adding a bunch of unnecessary blocks, clogging up the library. There needs to be a balance, and I believe Scratch currently has it.

That's why I still think this is a good solution.

[next v] costume ::looks
[previous v] costume ::looks

Don't make a new block, just update the one we have now so it makes more sense.

CosmicHamster

No support. The workaround only needs 3 blocks, which is really simple.

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

Just because it has a scary operator block in it does not mean it is hard. In my opinion, the work around should be very easy to remember. But if the

switch backdrop to [ v]

block has “previous backdrop” and “next backdrop” as some of the options, then I suppose that it could be an option for the

switch costume to [ v]

block, too. But I still think that the work around is easy.

Catgirl555

CosmicHamster wrote:
No support. The workaround only needs 3 blocks, which is really simple.
switch costume to <(costume #) - (1)>
Just because it has a scary operator block in it does not mean it is hard. In my opinion, the work around should be very easy to remember. But if the
switch backdrop to [ v]
block has “previous backdrop” and “next backdrop” as some of the options, then I suppose that it could be an option for the
switch costume to [ v]
block, too. But I still think that the work around is easy.

I don't think operators are scary.

Last edited by Catgirl555 (April 26, 2015 17:22:08)

CosmicHamster

Catgirl555 wrote:
CosmicHamster wrote:
No support. The workaround only needs 3 blocks, which is really simple.
switch costume to <(costume #) - (1)>
Just because it has a scary operator block in it does not mean it is hard. In my opinion, the work around should be very easy to remember. But if the
switch backdrop to [ v]
block has “previous backdrop” and “next backdrop” as some of the options, then I suppose that it could be an option for the
switch costume to [ v]
block, too. But I still think that the work around is easy.
I don't think operators are scary.

I know, but some people when they start Scratch think that operators are complicated, so I was referring to them.

Catgirl555

CosmicHamster wrote:
Catgirl555 wrote:
CosmicHamster wrote:
No support. The workaround only needs 3 blocks, which is really simple.
switch costume to <(costume #) - (1)>
Just because it has a scary operator block in it does not mean it is hard. In my opinion, the work around should be very easy to remember. But if the
switch backdrop to [ v]
block has “previous backdrop” and “next backdrop” as some of the options, then I suppose that it could be an option for the
switch costume to [ v]
block, too. But I still think that the work around is easy.
I don't think operators are scary.
I know, but some people when they start Scratch think that operators are complicated, so I was referring to them.

Oh, okay.

Discuss Scratch