reverse of <next costume> block?

therealpsy

like i dunno a <previous costume> block
i don't think it's fair that there is a next costume block and not one for previous costumes.
it would be cool for dubstep remixes and such
just saying

MegaApuTurkUltra

Support. This has been suggested before though, and on the other thread (I forget where it was) I suggested a “previous” and “next” option to the “switch costume” block, which wouldn't require major code changes (at least not as much as making a new block). I mean, the “switch backdrop” block has options for previous and next…

DaSpudLord

Duplicate of some other thread… I'm too lazy to go and find it though.

Anyway, no support, because you can just use this workaround-

matey1234

MegaApuTurkUltra wrote:
Support. This has been suggested before though, and on the other thread (I forget where it was) I suggested a “previous” and “next” option to the “switch costume” block, which wouldn't require major code changes (at least not as much as making a new block). I mean, the “switch backdrop” block has options for previous and next…

FalconGunner99

Duplicate of at least 420 other threads, but I still support.

Anything to satisfy my intense need to make my code minimalist.

therealpsy

DaSpudLord wrote:
Duplicate of some other thread… I'm too lazy to go and find it though.

Anyway, no support, because you can just use this workaround-

ok thanks

Cosmicstars-

Support for this:

Last edited by Cosmicstars- (May 23, 2015 21:35:32)

theonlygusti

Cosmicstars- wrote:
Support for this:

Braeden5454

DaSpudLord wrote:
Duplicate of some other thread… I'm too lazy to go and find it though.

Anyway, no support, because you can just use this workaround-

^^ Its better to let people code it themselves.
Sorry, no support

rollercoasterfan

DaSpudLord wrote:
Duplicate of some other thread… I'm too lazy to go and find it though.

Anyway, no support, because you can just use this workaround-

Okay, so you're saying we should remove the next costume block then because it has this workaround:

Support.

TheUniversalWorld1

I would support with the non-exsistent block:

chrissaisanidiot

Words cannot express how much I need this!
Support.

theonlygusti

DaSpudLord wrote:
Duplicate of some other thread… I'm too lazy to go and find it though.

Anyway, no support, because you can just use this workaround-

If you're too lazy to type two words into a search bar, then why are you willing to waste so much effort in using that ridiculous workaround every time?

I support, just because a block has a workaround doesn't mean it isn't useless.

thelucariokid

People have already suggested this, but it has been rejected because of:

Still, I give 50% support because new Scratchers would have lots of use for it

Last edited by thelucariokid (May 25, 2015 15:48:20)

Cool_Cat22

I think this script would be better:

DaSpudLord

theonlygusti wrote:
DaSpudLord wrote:
Duplicate of some other thread… I'm too lazy to go and find it though.

Anyway, no support, because you can just use this workaround-
If you're too lazy to type two words into a search bar, then why are you willing to waste so much effort in using that ridiculous workaround every time?

I support, just because a block has a workaround doesn't mean it isn't useless.

That's not just typing two words into a search bar. Using search would get me a bunch of old posts that died a long time ago, and I would want the most recent one (that way I don't start an argument about necroposting). To actually find it, I would have to open a new tab and scroll through each page searching for a suggestion I don't support. Meanwhile that “ridiculous workaround” requires 3 blocks. Only 3 blocks- two of which come from the same tab. But, if you're really lazy and don't feel like dragging 3 blocks out of the block pallete, you can always create a custom block.

Last edited by DaSpudLord (May 26, 2015 00:30:49)

nickydroids

Last edited by nickydroids (July 2, 2015 15:40:33)

samanyolu

You know, Scratch is about imagining, programming and sharing. Also, the programming part of Scratch is incredibly easy. Why are you trying to simplify most of the easy workarounds instead of improving yourself with coding even more?

No support because of the reason I gave above, and this simple workaround:

Last edited by samanyolu (July 2, 2015 15:55:21)

ev3coolexit987654

FalconGunner99 wrote:
Duplicate of at least 420 other threads, but I still support.

Anything to satisfy my intense need to make my code minimalist.

This

TheLogFather

MegaApuTurkUltra wrote:
…on the other thread (I forget where it was) I suggested a “previous” and “next” option to the “switch costume” block…

The switch costume block already recognises strings for next and previous costume:

It's actually hard-coded into the Scratch coding (so it doesn't go through any translation

):
https://github.com/LLK/scratch-flash/blob/master/src/primitives/LooksPrims.as#L103

(Bit of a surprise, right…? -Not sure it will stay like this, so wouldn't recommend actually using it.)
(Also, won't work in the rather unlikely event that you have a costume that matches the above strings - it will pick that costume name then.)

Last edited by TheLogFather (July 2, 2015 17:53:48)

Discuss Scratch